Re: Please add me to the contributor list

> On Feb 5, 2016, at 11:37 AM, Guozhang Wang wrote: > > Hi James, > > Just added you to JIRAs, but seems you do not have an id for wiki yet > (cannot find wushujames). Do you want to create one? > Thanks. I just created a login "wushujames" on the https://cwiki.apache.org/confluence/display/KAF

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135586#comment-15135586 ] Rajiv Kurian commented on KAFKA-3159: - Thanks Jason. I'll try to apply this patch earl

Jenkins build is back to normal : kafka-trunk-jdk7 #1025

See

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135356#comment-15135356 ] Jason Gustafson commented on KAFKA-3159: [~ra...@signalfx.com] We're still discuss

[jira] [Updated] (KAFKA-3215) controller may not be started when there are multiple ZK session expirations

[ https://issues.apache.org/jira/browse/KAFKA-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3215: --- Labels: controller (was: ) > controller may not be started when there are multiple ZK session expirat

Build failed in Jenkins: kafka-trunk-jdk8 #353

See Changes: [me] MINOR: Improve error message for inconsistent broker ids -- [...truncated 4886 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[0] PASSED kafka.log.Broker

[jira] [Created] (KAFKA-3215) controller may not be started when there are multiple ZK session expirations

Jun Rao created KAFKA-3215: -- Summary: controller may not be started when there are multiple ZK session expirations Key: KAFKA-3215 URL: https://issues.apache.org/jira/browse/KAFKA-3215 Project: Kafka

[jira] [Commented] (KAFKA-3190) KafkaProducer should not invoke callback in send()

[ https://issues.apache.org/jira/browse/KAFKA-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135289#comment-15135289 ] ASF GitHub Bot commented on KAFKA-3190: --- GitHub user becketqin opened a pull request

[GitHub] kafka pull request: KAFKA-3190 Producer should not fire callback i...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/880 KAFKA-3190 Producer should not fire callback in Send() method @guozhangwang Would you mind take a look? This was originally introduced in KAFKA-1260. I did not find specific reason in the original

Re: Kafka 0.9.0.1 plan

Hi Allen, As the JIRA says, KAFKA-3100 has already been integrated into the 0.9.0 branch and will be part of 0.9.0.1. Ismael On Fri, Feb 5, 2016 at 10:49 PM, Allen Wang wrote: > Hi Jun, > > What about https://issues.apache.org/jira/browse/KAFKA-3100? > > Thanks, > Allen > > > On Fri, Feb 5, 20

[GitHub] kafka pull request: MINOR: Improve error message for inconsistent ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/847 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

Re: Kafka 0.9.0.1 plan

Hi Jun, What about https://issues.apache.org/jira/browse/KAFKA-3100? Thanks, Allen On Fri, Feb 5, 2016 at 1:19 PM, Ismael Juma wrote: > Hi Becket, > > On Fri, Feb 5, 2016 at 9:15 PM, Becket Qin wrote: > > > I am taking KAFKA-3177 off the list because the correct fix might involve > > some re

Jenkins build is back to normal : kafka-trunk-jdk8 #352

See

Build failed in Jenkins: kafka-trunk-jdk7 #1024

See Changes: [me] MINOR: Add more info to RecordCollector error message [me] KAFKA-3037: Test number of alive brokers known after single node [me] KAFKA-2589: The default value for the "rebalance.backoff.ms" property ---

Build failed in Jenkins: kafka_0.9.0_jdk7 #115

See Changes: [me] KAFKA-2589: The default value for the "rebalance.backoff.ms" property [me] MINOR: Updated kafkatest version to match version specified in -- Started by an SCM change [EnvInject

[GitHub] kafka pull request: MINOR: Updated kafkatest version to match vers...

Github user granders closed the pull request at: https://github.com/apache/kafka/pull/878 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[GitHub] kafka pull request: MINOR: Add note about which files need to be e...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/879 MINOR: Add note about which files need to be edited when updating the version number You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka

[jira] [Updated] (KAFKA-2589) Documentation bug: the default value for the "rebalance.backoff.ms" property is not specified correctly

[ https://issues.apache.org/jira/browse/KAFKA-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-2589: - Resolution: Fixed Fix Version/s: 0.9.1.0 0.9.0.1

[jira] [Commented] (KAFKA-2589) Documentation bug: the default value for the "rebalance.backoff.ms" property is not specified correctly

[ https://issues.apache.org/jira/browse/KAFKA-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135033#comment-15135033 ] ASF GitHub Bot commented on KAFKA-2589: --- Github user asfgit closed the pull request

[GitHub] kafka pull request: KAFKA-2589: the default value for the "rebalan...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/876 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Updated] (KAFKA-2784) Mirror maker should swallow exceptions during shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2784: --- Fix Version/s: 0.9.1.0 > Mirror maker should swallow exceptions during shutdown. > ---

Re: Kafka 0.9.0.1 plan

Hi Becket, On Fri, Feb 5, 2016 at 9:15 PM, Becket Qin wrote: > I am taking KAFKA-3177 off the list because the correct fix might involve > some refactoring of exception hierarchy in new consumer. That may take some > time and 0.9.0.1 probably does not need to block on it. > Sounds good to me.

[jira] [Updated] (KAFKA-3037) Number of alive brokers not known after single node cluster startup

[ https://issues.apache.org/jira/browse/KAFKA-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3037: - Resolution: Fixed Fix Version/s: 0.9.1.0 Status: Resolved (was:

[jira] [Commented] (KAFKA-3037) Number of alive brokers not known after single node cluster startup

[ https://issues.apache.org/jira/browse/KAFKA-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135015#comment-15135015 ] ASF GitHub Bot commented on KAFKA-3037: --- Github user asfgit closed the pull request

[GitHub] kafka pull request: KAFKA-3037: Test number of alive brokers known...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/875 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

Re: Kafka 0.9.0.1 plan

Hi Jun, I am taking KAFKA-3177 off the list because the correct fix might involve some refactoring of exception hierarchy in new consumer. That may take some time and 0.9.0.1 probably does not need to block on it. Please let me know if you think we should have it fixed in 0.9.0.1. Thanks, Jiang

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135007#comment-15135007 ] Ismael Juma commented on KAFKA-3159: For reference, Jun also added a comment to the or

[jira] [Updated] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3177: Fix Version/s: (was: 0.9.0.1) 0.9.1.0 > Kafka consumer can hang when position

[jira] [Commented] (KAFKA-3091) Broker with an invalid id would not start when its id is updated to a new valid one

[ https://issues.apache.org/jira/browse/KAFKA-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134995#comment-15134995 ] Vahid Hashemian commented on KAFKA-3091: [~granthenke] Just saw your note after my

[jira] [Commented] (KAFKA-3091) Broker with an invalid id would not start when its id is updated to a new valid one

[ https://issues.apache.org/jira/browse/KAFKA-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134993#comment-15134993 ] Vahid Hashemian commented on KAFKA-3091: Never mind. I updated the {{broker.id}} p

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134991#comment-15134991 ] Jason Gustafson commented on KAFKA-3159: Talked with [~junrao] offline about this.

[GitHub] kafka pull request: MINOR: Updated kafkatest version to match vers...

GitHub user granders opened a pull request: https://github.com/apache/kafka/pull/878 MINOR: Updated kafkatest version to match version specified in gradle.properties This discrepancy was causing a few system tests which to some version validation to fail consistently on 0.9.0 branc

[jira] [Commented] (KAFKA-3091) Broker with an invalid id would not start when its id is updated to a new valid one

[ https://issues.apache.org/jira/browse/KAFKA-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134977#comment-15134977 ] Grant Henke commented on KAFKA-3091: [~vahid] Just remove any files in the configured

[GitHub] kafka pull request: MINOR: more info in error msg

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/873 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Commented] (KAFKA-3091) Broker with an invalid id would not start when its id is updated to a new valid one

[ https://issues.apache.org/jira/browse/KAFKA-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134963#comment-15134963 ] Vahid Hashemian commented on KAFKA-3091: If I have version 0.9.0 running and run i

Build failed in Jenkins: kafka-trunk-jdk7 #1023

See Changes: [me] KAFKA-3165: Fix ignored parameters in the gradle "All" tasks -- [...truncated 2797 lines...] kafka.log.FileMessageSetTest > testIterationDoesntChangePosition PASSED kafka.log

[GitHub] kafka pull request: HOTFIX: fix streams issues

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/877 HOTFIX: fix streams issues * RocksDBStore.putInternal should by pass logging. * StoreChangeLogger should not call context.recordCollector() when nothing to log * This is for standby tasks.

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134836#comment-15134836 ] Jiangjie Qin commented on KAFKA-3197: - [~ijuma] Sure, we can target it 0.9.1.0. Last m

[jira] [Updated] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3197: Fix Version/s: (was: 0.9.0.1) 0.9.1.0 > Producer can send message out of orde

Re: Consumer Assignment documentation - StreamPartitionAssignment.java

Hi Vamsi, Kafka Streams uses the new 0.9.0 Java consumer as its underlying client, which do not have ZK dependency anymore. Instead it relies on a coordinator on the server side, one assigned for each consumer group to assign partitions among themselves. You can find more details here: https://c

Re: Please add me to the contributor list

Hi James, Just added you to JIRAs, but seems you do not have an id for wiki yet (cannot find wushujames). Do you want to create one? Guozhang On Fri, Feb 5, 2016 at 9:51 AM, James Cheng wrote: > Hi, > > I'd like to be able to file and assign JIRAs to myself to make some docs. > Can you please

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134813#comment-15134813 ] Rajiv Kurian commented on KAFKA-3159: - Though I should mention that I've seen the same

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134809#comment-15134809 ] Jason Gustafson commented on KAFKA-3159: [~granthenke] Thanks for the suggestion,

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134776#comment-15134776 ] Rajiv Kurian commented on KAFKA-3159: - It does seem like it is related if not the same

[jira] [Commented] (KAFKA-3088) 0.9.0.0 broker crash on receipt of produce request with empty client ID

[ https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134778#comment-15134778 ] Grant Henke commented on KAFKA-3088: [~ijuma] As soon as the general approach and code

Build failed in Jenkins: kafka-trunk-jdk8 #351

See Changes: [me] KAFKA-3165: Fix ignored parameters in the gradle "All" tasks -- [...truncated 82 lines...] /x1/jenkins/jenkins-slave/workspace/kafka-trunk-jdk8/core/src/main/scala/kafka/server/

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134768#comment-15134768 ] Grant Henke commented on KAFKA-3159: Could this be related to KAFKA-3003? A fix for KA

[jira] [Commented] (KAFKA-3088) 0.9.0.0 broker crash on receipt of produce request with empty client ID

[ https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134769#comment-15134769 ] Ismael Juma commented on KAFKA-3088: [~granthenke], you may have seen that 0.9.0.1 is

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134760#comment-15134760 ] Ismael Juma commented on KAFKA-3197: [~becket_qin], the plan is to release 0.9.0.1 nex

[jira] [Comment Edited] (KAFKA-2948) Kafka producer does not cope well with topic deletions

[ https://issues.apache.org/jira/browse/KAFKA-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134705#comment-15134705 ] Ismael Juma edited comment on KAFKA-2948 at 2/5/16 7:05 PM: Se

[jira] [Commented] (KAFKA-2948) Kafka producer does not cope well with topic deletions

[ https://issues.apache.org/jira/browse/KAFKA-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134705#comment-15134705 ] Ismael Juma commented on KAFKA-2948: Setting target as 0.9.1.0 as 0.9.0.1 will be rele

[jira] [Updated] (KAFKA-2948) Kafka producer does not cope well with topic deletions

[ https://issues.apache.org/jira/browse/KAFKA-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2948: --- Fix Version/s: (was: 0.9.0.1) 0.9.1.0 > Kafka producer does not cope well with

[jira] [Updated] (KAFKA-3165) Fix ignored parameters in the gradle "All" tasks

[ https://issues.apache.org/jira/browse/KAFKA-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3165: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

[GitHub] kafka pull request: KAFKA-3165: Fix ignored parameters in the grad...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/835 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Commented] (KAFKA-3165) Fix ignored parameters in the gradle "All" tasks

[ https://issues.apache.org/jira/browse/KAFKA-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134664#comment-15134664 ] ASF GitHub Bot commented on KAFKA-3165: --- Github user asfgit closed the pull request

Kafka 0.9.0.1 plan

Hi, Everyone, We have fixed a few critical bugs since 0.9.0.0 was released and are still investigating a few more issues. The current list of issues tracked for 0.9.0.1 can be found below. Among them, only KAFKA-3159 seems to be critical. https://issues.apache.org/jira/issues/?jql=project%20%3D%2

Re: Consumer Assignment documentation - StreamPartitionAssignment.java

Thanks Guozhang. Is the below true? 1. There is no central controller for the consuemrs which assigns the partitions to the active consumers. 2. Hence, the consumers each fight for the allocation by registering the watch on active consumers (/ids path in zk). But how do the consumers finally arr

Please add me to the contributor list

Hi, I'd like to be able to file and assign JIRAs to myself to make some docs. Can you please add me to the contributor list? My Apache JIRA username is wushujames. Thanks, -James This email and any attachments may contain confidential and privileged material

[jira] [Comment Edited] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134562#comment-15134562 ] Rajiv Kurian edited comment on KAFKA-3159 at 2/5/16 5:49 PM: -

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134562#comment-15134562 ] Rajiv Kurian commented on KAFKA-3159: - I think I've found the isse. It turns out that

Build failed in Jenkins: kafka-trunk-jdk7 #1022

See Changes: [wangguoz] KAFKA-3003: Update the replica.highWatermark correctly [wangguoz] KAFKA-3157: Mirror maker doesn't commit offset with low traffic -- Started by an SCM change [EnvInject]

Build failed in Jenkins: kafka_0.9.0_jdk7 #114

See Changes: [wangguoz] KAFKA-3003: Update the replica.highWatermark correctly [wangguoz] KAFKA-3157: Mirror maker doesn't commit offset with low traffic -- Started by an SCM change [EnvInject]

Build failed in Jenkins: kafka-trunk-jdk8 #350

See Changes: [wangguoz] KAFKA-3003: Update the replica.highWatermark correctly [wangguoz] KAFKA-3157: Mirror maker doesn't commit offset with low traffic -- Started by an SCM change [EnvInject]

[jira] [Updated] (KAFKA-3157) Mirror maker doesn't commit offset with new consumer when there is no more messages

[ https://issues.apache.org/jira/browse/KAFKA-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3157: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[jira] [Commented] (KAFKA-3157) Mirror maker doesn't commit offset with new consumer when there is no more messages

[ https://issues.apache.org/jira/browse/KAFKA-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134493#comment-15134493 ] ASF GitHub Bot commented on KAFKA-3157: --- Github user asfgit closed the pull request

[GitHub] kafka pull request: KAFKA-3157 - Mirror maker doesn't commit offse...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/821 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Commented] (KAFKA-3003) The fetch.wait.max.ms is not honored when new log segment rolled for low volume topics.

[ https://issues.apache.org/jira/browse/KAFKA-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134488#comment-15134488 ] ASF GitHub Bot commented on KAFKA-3003: --- Github user asfgit closed the pull request

[GitHub] kafka pull request: KAFKA-3003 Update the replica.highWatermark co...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/688 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Updated] (KAFKA-3003) The fetch.wait.max.ms is not honored when new log segment rolled for low volume topics.

[ https://issues.apache.org/jira/browse/KAFKA-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3003: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[jira] [Commented] (KAFKA-3088) 0.9.0.0 broker crash on receipt of produce request with empty client ID

[ https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134396#comment-15134396 ] Grant Henke commented on KAFKA-3088: [~ijuma] Yes, after the trunk patch is reviewed,

[jira] [Commented] (KAFKA-3088) 0.9.0.0 broker crash on receipt of produce request with empty client ID

[ https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134390#comment-15134390 ] Ismael Juma commented on KAFKA-3088: Thanks [~granthenke]. Are you planning to submit

Offset Commit/Fetch API documentation

Hi there, I want to implement the Offset Commit/Fetch api functionality in our in house .net client. https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-OffsetCommit/FetchAPI It seems the documentation is incomplete and clearly not of the sam

[jira] [Comment Edited] (KAFKA-2904) Consumer Fails to Reconnect after 30s post restarts

[ https://issues.apache.org/jira/browse/KAFKA-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134158#comment-15134158 ] Simon Cooper edited comment on KAFKA-2904 at 2/5/16 1:24 PM: -

[jira] [Commented] (KAFKA-2904) Consumer Fails to Reconnect after 30s post restarts

[ https://issues.apache.org/jira/browse/KAFKA-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134158#comment-15134158 ] Simon Cooper commented on KAFKA-2904: - We've seen a similar issue when first starting

[jira] [Commented] (KAFKA-3206) No reconsiliation after partitioning

[ https://issues.apache.org/jira/browse/KAFKA-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133838#comment-15133838 ] Arkadiusz Firus commented on KAFKA-3206: [~xiaotao183] The "unclean.leader.electio

[jira] [Commented] (KAFKA-3179) Kafka consumer delivers message whose offset is earlier than sought offset.

[ https://issues.apache.org/jira/browse/KAFKA-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133817#comment-15133817 ] Ismael Juma commented on KAFKA-3179: Joel also committed it to 0.9.0: https://github.

[jira] [Updated] (KAFKA-3179) Kafka consumer delivers message whose offset is earlier than sought offset.

[ https://issues.apache.org/jira/browse/KAFKA-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3179: --- Fix Version/s: 0.9.0.1 > Kafka consumer delivers message whose offset is earlier than sought offset. >