[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323299#comment-15323299 ] Evan Huus commented on KAFKA-2082: -- This issue has been "In Progress" since April 2015, a

[jira] [Commented] (KAFKA-3289) Update Kafka protocol guide wiki for KIP-31 / KIP-32

[ https://issues.apache.org/jira/browse/KAFKA-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174318#comment-15174318 ] Evan Huus commented on KAFKA-3289: -- OK, I commented there because I didn't know this tick

[jira] [Created] (KAFKA-2871) Newly replicated brokers don't expire log segments properly

Evan Huus created KAFKA-2871: Summary: Newly replicated brokers don't expire log segments properly Key: KAFKA-2871 URL: https://issues.apache.org/jira/browse/KAFKA-2871 Project: Kafka Issue Type

[jira] [Created] (KAFKA-2537) Mirrormaker defaults to localhost with no sanity checks

Evan Huus created KAFKA-2537: Summary: Mirrormaker defaults to localhost with no sanity checks Key: KAFKA-2537 URL: https://issues.apache.org/jira/browse/KAFKA-2537 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574985#comment-14574985 ] Evan Huus commented on KAFKA-2147: -- We have rolled out a custom build with this patch to

[jira] [Updated] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-2147: - Attachment: purgatory.log.gz Results from testing the most recent branch are *very* promising. We will rol

[jira] [Updated] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-2147: - Attachment: purgatory.log Purgatory log from the attached patch. Based on my understanding, the check is

[jira] [Commented] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543761#comment-14543761 ] Evan Huus commented on KAFKA-2147: -- OK, it appears the patch does not fix this issue, we

[jira] [Commented] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543666#comment-14543666 ] Evan Huus commented on KAFKA-2147: -- Increasing the producer batch size has substantially

[jira] [Updated] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-2147: - Attachment: watch-lists.log watch list purging logs > Unbalanced replication can cause extreme purgatory

[jira] [Comment Edited] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540669#comment-14540669 ] Evan Huus edited comment on KAFKA-2147 at 5/12/15 8:43 PM: --- 1. 1

[jira] [Commented] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540669#comment-14540669 ] Evan Huus commented on KAFKA-2147: -- 1. 150-200 base on a quick wireshark capture 2. Thou

[jira] [Commented] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540218#comment-14540218 ] Evan Huus commented on KAFKA-2147: -- 1. 4-8k messages/s snappy-compressed, taking 2.5-5 MB

[jira] [Comment Edited] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521670#comment-14521670 ] Evan Huus edited comment on KAFKA-2147 at 4/30/15 4:13 PM: --- When

[jira] [Comment Edited] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521670#comment-14521670 ] Evan Huus edited comment on KAFKA-2147 at 4/30/15 4:12 PM: --- When

[jira] [Commented] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521670#comment-14521670 ] Evan Huus commented on KAFKA-2147: -- When I enable TRACE request logging on a single node

[jira] [Comment Edited] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514302#comment-14514302 ] Evan Huus edited comment on KAFKA-2147 at 4/27/15 3:38 PM: --- h5.

[jira] [Comment Edited] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514302#comment-14514302 ] Evan Huus edited comment on KAFKA-2147 at 4/27/15 3:35 PM: --- h5.

[jira] [Commented] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514302#comment-14514302 ] Evan Huus commented on KAFKA-2147: -- h5. Case 3 - Second Cluster As I mentioned above, we

[jira] [Commented] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

[ https://issues.apache.org/jira/browse/KAFKA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514225#comment-14514225 ] Evan Huus commented on KAFKA-2147: -- Ah, OK. We are running with entirely default replicat

[jira] [Created] (KAFKA-2147) Unbalanced replication can cause extreme purgatory growth

Evan Huus created KAFKA-2147: Summary: Unbalanced replication can cause extreme purgatory growth Key: KAFKA-2147 URL: https://issues.apache.org/jira/browse/KAFKA-2147 Project: Kafka Issue Type: B

[jira] [Resolved] (KAFKA-1033) Metadata requests do not always return the complete list of available brokers

[ https://issues.apache.org/jira/browse/KAFKA-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus resolved KAFKA-1033. -- Resolution: Not A Problem > Metadata requests do not always return the complete list of available broker

[jira] [Updated] (KAFKA-2143) Replicas get ahead of leader and fail

[ https://issues.apache.org/jira/browse/KAFKA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-2143: - Description: On a cluster of 6 nodes, we recently saw a case where a single under-replicated partition su

[jira] [Created] (KAFKA-2143) Replicas get ahead of leader and fail

Evan Huus created KAFKA-2143: Summary: Replicas get ahead of leader and fail Key: KAFKA-2143 URL: https://issues.apache.org/jira/browse/KAFKA-2143 Project: Kafka Issue Type: Bug Compone

[jira] [Comment Edited] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483482#comment-14483482 ] Evan Huus edited comment on KAFKA-2082 at 4/7/15 4:49 PM: -- OK, ye

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483482#comment-14483482 ] Evan Huus commented on KAFKA-2082: -- OK, yes, if I wait long enough (2-3 minutes) then it

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483421#comment-14483421 ] Evan Huus commented on KAFKA-2082: -- At what point will it recover? I've let it run for a

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482421#comment-14482421 ] Evan Huus commented on KAFKA-2082: -- 1. Then why does broker3 continue to spam logs? (I un

[jira] [Issue Comment Deleted] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-2082: - Comment: was deleted (was: OK, that all makes sense. Some follow-up questions: 1. When the cluster heals

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482302#comment-14482302 ] Evan Huus commented on KAFKA-2082: -- OK, that all makes sense. Some follow-up questions:

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482301#comment-14482301 ] Evan Huus commented on KAFKA-2082: -- OK, that all makes sense. Some follow-up questions:

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482058#comment-14482058 ] Evan Huus commented on KAFKA-2082: -- What if (in a normally set up cluster) a broker becom

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481981#comment-14481981 ] Evan Huus commented on KAFKA-2082: -- So I guess the producer should not be connecting to b

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396024#comment-14396024 ] Evan Huus commented on KAFKA-2082: -- If the root of this bug is the controller not returni

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395847#comment-14395847 ] Evan Huus commented on KAFKA-2082: -- Hmm, the test is configured to retry a message 5 time

[jira] [Updated] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-2082: - Description: While running integration tests for Sarama (the go client) we came across a pattern of conne

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392017#comment-14392017 ] Evan Huus commented on KAFKA-2082: -- I have pushed another branch called {{test-jira-kafka

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391877#comment-14391877 ] Evan Huus commented on KAFKA-2082: -- The 3GB is only set if you use VMware fusion, if you

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391607#comment-14391607 ] Evan Huus commented on KAFKA-2082: -- We are using ZK connection drops as a convenient way

[jira] [Updated] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-2082: - Description: While running integration tests for Sarama (the go client) we came across a pattern of conne

[jira] [Updated] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-2082: - Description: While running integration tests for Sarama (the go client) we came across a pattern of conne

[jira] [Updated] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-2082: - Description: While running integration tests for Sarama (the go client) we came across a pattern of conne

[jira] [Updated] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-2082: - Description: While running integration tests for Sarama (the go client) we came across a pattern of conne

[jira] [Created] (KAFKA-2082) Kafka Replication ends up in a bad state

Evan Huus created KAFKA-2082: Summary: Kafka Replication ends up in a bad state Key: KAFKA-2082 URL: https://issues.apache.org/jira/browse/KAFKA-2082 Project: Kafka Issue Type: Bug Comp

[jira] [Commented] (KAFKA-1998) Partitions Missing From MetadataResponse

[ https://issues.apache.org/jira/browse/KAFKA-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348072#comment-14348072 ] Evan Huus commented on KAFKA-1998: -- It's no longer clear to me, based on [~junrao]'s foll

[jira] [Created] (KAFKA-1998) Partitions Missing From MetadataResponse

Evan Huus created KAFKA-1998: Summary: Partitions Missing From MetadataResponse Key: KAFKA-1998 URL: https://issues.apache.org/jira/browse/KAFKA-1998 Project: Kafka Issue Type: Bug Comp

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311387#comment-14311387 ] Evan Huus commented on KAFKA-1718: -- [~guozhang], [~jkreps] my understanding is that while

[jira] [Commented] (KAFKA-1806) broker can still expose uncommitted data to a consumer

[ https://issues.apache.org/jira/browse/KAFKA-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248764#comment-14248764 ] Evan Huus commented on KAFKA-1806: -- Sarama client maintainer here (via https://github.co

[jira] [Comment Edited] (KAFKA-1744) Fetch Response contains messages prior to the requested offset

[ https://issues.apache.org/jira/browse/KAFKA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201425#comment-14201425 ] Evan Huus edited comment on KAFKA-1744 at 11/7/14 2:00 AM: --- [~ju

[jira] [Resolved] (KAFKA-1744) Fetch Response contains messages prior to the requested offset

[ https://issues.apache.org/jira/browse/KAFKA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus resolved KAFKA-1744. -- Resolution: Fixed > Fetch Response contains messages prior to the requested offset > ---

[jira] [Commented] (KAFKA-1744) Fetch Response contains messages prior to the requested offset

[ https://issues.apache.org/jira/browse/KAFKA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201425#comment-14201425 ] Evan Huus commented on KAFKA-1744: -- [~junrao] very nice stealth edit of the spec, thank y

[jira] [Commented] (KAFKA-1744) Fetch Response contains messages prior to the requested offset

[ https://issues.apache.org/jira/browse/KAFKA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201374#comment-14201374 ] Evan Huus commented on KAFKA-1744: -- [~nehanarkhede] this was discovered in the golang con

[jira] [Created] (KAFKA-1744) Fetch Response contains messages prior to the requested offset

Evan Huus created KAFKA-1744: Summary: Fetch Response contains messages prior to the requested offset Key: KAFKA-1744 URL: https://issues.apache.org/jira/browse/KAFKA-1744 Project: Kafka Issue T

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181348#comment-14181348 ] Evan Huus commented on KAFKA-1718: -- [~junrao] I already have wiki permissions, so I made

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180126#comment-14180126 ] Evan Huus commented on KAFKA-1718: -- ??when it gets a partial message from the broker it w

[jira] [Comment Edited] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180126#comment-14180126 ] Evan Huus edited comment on KAFKA-1718 at 10/22/14 4:22 PM: ??

[jira] [Comment Edited] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179485#comment-14179485 ] Evan Huus edited comment on KAFKA-1718 at 10/22/14 2:26 AM: ??

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179485#comment-14179485 ] Evan Huus commented on KAFKA-1718: -- ??I guess your go producer can send multiple compress

[jira] [Comment Edited] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177487#comment-14177487 ] Evan Huus edited comment on KAFKA-1718 at 10/20/14 9:23 PM: Th

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177487#comment-14177487 ] Evan Huus commented on KAFKA-1718: -- That sounds plausible. 1. How do I verify if that is

[jira] [Comment Edited] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177351#comment-14177351 ] Evan Huus edited comment on KAFKA-1718 at 10/20/14 7:28 PM: Th

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177351#comment-14177351 ] Evan Huus commented on KAFKA-1718: -- The numbers I put in my original report do take all o

[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177112#comment-14177112 ] Evan Huus commented on KAFKA-1718: -- LogOverhead is only 12 bytes; none of the values I pr

[jira] [Created] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy

Evan Huus created KAFKA-1718: Summary: "Message Size Too Large" error when only small messages produced with Snappy Key: KAFKA-1718 URL: https://issues.apache.org/jira/browse/KAFKA-1718 Project: Kafka

[jira] [Commented] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818523#comment-13818523 ] Evan Huus commented on KAFKA-1110: -- My ICLA has been accepted, and my name appears on the

[jira] [Commented] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817533#comment-13817533 ] Evan Huus commented on KAFKA-1110: -- This bug can now track the fact that a compressed mes

[jira] [Commented] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817532#comment-13817532 ] Evan Huus commented on KAFKA-1110: -- ICLA submitted. Don't know how long it will take me t

[jira] [Commented] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817504#comment-13817504 ] Evan Huus commented on KAFKA-1110: -- I've made changes to that page in the past but I gues

[jira] [Commented] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817480#comment-13817480 ] Evan Huus commented on KAFKA-1110: -- Bitwise and is commutative, so (mask & value) is alwa

[jira] [Commented] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817478#comment-13817478 ] Evan Huus commented on KAFKA-1110: -- I have verified that I have log4j in the path, and am

[jira] [Commented] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817414#comment-13817414 ] Evan Huus commented on KAFKA-1110: -- The 0x07 is the same as the CompressionCodeMask in th

[jira] [Commented] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816949#comment-13816949 ] Evan Huus commented on KAFKA-1110: -- I don't know how to make it work. The provided Consol

[jira] [Comment Edited] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809464#comment-13809464 ] Evan Huus edited comment on KAFKA-1110 at 11/6/13 6:32 PM: --- I am

[jira] [Comment Edited] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815127#comment-13815127 ] Evan Huus edited comment on KAFKA-1110 at 11/6/13 6:32 PM: --- Hi J

[jira] [Comment Edited] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815127#comment-13815127 ] Evan Huus edited comment on KAFKA-1110 at 11/6/13 6:31 PM: --- Hi J

[jira] [Commented] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815127#comment-13815127 ] Evan Huus commented on KAFKA-1110: -- Hi Joe, as verified with the network trace, Sarama is

[jira] [Commented] (KAFKA-1110) Unable to produce messages with snappy/gzip compression

[ https://issues.apache.org/jira/browse/KAFKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809464#comment-13809464 ] Evan Huus commented on KAFKA-1110: -- I am the primary author of the golang library and the

[jira] [Created] (KAFKA-1033) Metadata requests do not always return the complete list of available brokers

Evan Huus created KAFKA-1033: Summary: Metadata requests do not always return the complete list of available brokers Key: KAFKA-1033 URL: https://issues.apache.org/jira/browse/KAFKA-1033 Project: Kafka

[jira] [Resolved] (KAFKA-993) Offset Management API is either broken or mis-documented

[ https://issues.apache.org/jira/browse/KAFKA-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus resolved KAFKA-993. - Resolution: Fixed > Offset Management API is either broken or mis-documented > ---

[jira] [Commented] (KAFKA-993) Offset Management API is either broken or mis-documented

[ https://issues.apache.org/jira/browse/KAFKA-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746033#comment-13746033 ] Evan Huus commented on KAFKA-993: - I have updated the protocol wiki to note that these APIs

[jira] [Commented] (KAFKA-993) Offset Management API is either broken or mis-documented

[ https://issues.apache.org/jira/browse/KAFKA-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745303#comment-13745303 ] Evan Huus commented on KAFKA-993: - The library is now available at https://github.com/Shopi

[jira] [Created] (KAFKA-993) Offset Management API is either broken or mis-documented

Evan Huus created KAFKA-993: --- Summary: Offset Management API is either broken or mis-documented Key: KAFKA-993 URL: https://issues.apache.org/jira/browse/KAFKA-993 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-993) Offset Management API is either broken or mis-documented

[ https://issues.apache.org/jira/browse/KAFKA-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Huus updated KAFKA-993: Description: I am in the process of building a set of Go client bindings for the new 0.8 protocol (https:/