[jira] [Commented] (KAFKA-2260) Allow specifying expected offset on produce

[ https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559225#comment-16559225 ] Andy Bryant commented on KAFKA-2260:  Would prove very handy in event source based designs > Allow

[jira] [Commented] (KAFKA-7207) Make rate & total metrics documentation consistent

[ https://issues.apache.org/jira/browse/KAFKA-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559105#comment-16559105 ] ASF GitHub Bot commented on KAFKA-7207: --- KevinLiLu opened a new pull request #5429: KAFKA-7207:

[jira] [Updated] (KAFKA-7192) State-store can desynchronise with changelog

[ https://issues.apache.org/jira/browse/KAFKA-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-7192: - Fix Version/s: 2.1.0 > State-store can desynchronise with changelog >

[jira] [Resolved] (KAFKA-7192) State-store can desynchronise with changelog

[ https://issues.apache.org/jira/browse/KAFKA-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7192. -- Resolution: Fixed > State-store can desynchronise with changelog >

[jira] [Commented] (KAFKA-7192) State-store can desynchronise with changelog

[ https://issues.apache.org/jira/browse/KAFKA-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559096#comment-16559096 ] ASF GitHub Bot commented on KAFKA-7192: --- guozhangwang closed pull request #5421: KAFKA-7192: Wipe

[jira] [Commented] (KAFKA-3514) Stream timestamp computation needs some further thoughts

[ https://issues.apache.org/jira/browse/KAFKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559039#comment-16559039 ] ASF GitHub Bot commented on KAFKA-3514: --- guozhangwang opened a new pull request #5428: KAFKA-3514:

[jira] [Updated] (KAFKA-5875) Consumer group repeatedly fails to join, even across JVM restarts: BufferUnderFlowException reading the {{version}} field in the consumer protocol header

[ https://issues.apache.org/jira/browse/KAFKA-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated KAFKA-5875: -- Component/s: consumer > Consumer group repeatedly fails to join, even across JVM restarts: >

[jira] [Commented] (KAFKA-7209) Kafka stream does not rebalance when one node gets down

[ https://issues.apache.org/jira/browse/KAFKA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558874#comment-16558874 ] Yogesh BG commented on KAFKA-7209: -- Here are observation 3 broker and 3 stream app - initially working

[jira] [Assigned] (KAFKA-5662) We should be able to specify min.insync.replicas for the __consumer_offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski reassigned KAFKA-5662: -- Assignee: Stanislav Kozlovski > We should be able to specify

[jira] [Comment Edited] (KAFKA-3841) MirrorMaker topic renaming

[ https://issues.apache.org/jira/browse/KAFKA-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558795#comment-16558795 ] David edited comment on KAFKA-3841 at 7/26/18 7:29 PM: --- Just wanted to mention

[jira] [Commented] (KAFKA-3841) MirrorMaker topic renaming

[ https://issues.apache.org/jira/browse/KAFKA-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558795#comment-16558795 ] David commented on KAFKA-3841: -- Just wanted to mention related info about the MessageHandler option: 

[jira] [Commented] (KAFKA-7209) Kafka stream does not rebalance when one node gets down

[ https://issues.apache.org/jira/browse/KAFKA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558772#comment-16558772 ] Yogesh BG commented on KAFKA-7209: -- in one of the forum i see below statement, does this impact

[jira] [Comment Edited] (KAFKA-7209) Kafka stream does not rebalance when one node gets down

[ https://issues.apache.org/jira/browse/KAFKA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558752#comment-16558752 ] Yogesh BG edited comment on KAFKA-7209 at 7/26/18 6:51 PM: --- when i kill the one

[jira] [Commented] (KAFKA-7209) Kafka stream does not rebalance when one node gets down

[ https://issues.apache.org/jira/browse/KAFKA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558748#comment-16558748 ] Matthias J. Sax commented on KAFKA-7209: Would be good to verify. If broker-only and streams-only

[jira] [Commented] (KAFKA-7209) Kafka stream does not rebalance when one node gets down

[ https://issues.apache.org/jira/browse/KAFKA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558731#comment-16558731 ] Yogesh BG commented on KAFKA-7209: -- is there any manual work around for this to resolve? i think killing

[jira] [Commented] (KAFKA-6014) new consumer mirror maker halts after committing offsets to a deleted topic

[ https://issues.apache.org/jira/browse/KAFKA-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558706#comment-16558706 ] Jason Gustafson commented on KAFKA-6014: [~felixgv] It's a good question. In the worst case, it

[jira] [Created] (KAFKA-7211) MM should handle timeouts in commitSync

Jason Gustafson created KAFKA-7211: -- Summary: MM should handle timeouts in commitSync Key: KAFKA-7211 URL: https://issues.apache.org/jira/browse/KAFKA-7211 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-7209) Kafka stream does not rebalance when one node gets down

[ https://issues.apache.org/jira/browse/KAFKA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558702#comment-16558702 ] Matthias J. Sax commented on KAFKA-7209: Not sure atm. Note, that it is not recommended to run

[jira] [Created] (KAFKA-7210) Add system test for log compaction

Manikumar created KAFKA-7210: Summary: Add system test for log compaction Key: KAFKA-7210 URL: https://issues.apache.org/jira/browse/KAFKA-7210 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-7126) Reduce number of rebalance for large consumer groups after a topic is created

[ https://issues.apache.org/jira/browse/KAFKA-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7126. - Resolution: Fixed > Reduce number of rebalance for large consumer groups after a topic is created >

[jira] [Updated] (KAFKA-7126) Reduce number of rebalance for large consumer groups after a topic is created

[ https://issues.apache.org/jira/browse/KAFKA-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7126: Summary: Reduce number of rebalance for large consumer groups after a topic is created (was: Reduce

[jira] [Commented] (KAFKA-7126) Reduce number of rebalance period for large consumer groups after a topic is created

[ https://issues.apache.org/jira/browse/KAFKA-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558652#comment-16558652 ] ASF GitHub Bot commented on KAFKA-7126: --- lindong28 closed pull request #5408: KAFKA-7126: Reduce

[jira] [Created] (KAFKA-7209) Kafka stream does not rebalance when one node gets down

Yogesh BG created KAFKA-7209: Summary: Kafka stream does not rebalance when one node gets down Key: KAFKA-7209 URL: https://issues.apache.org/jira/browse/KAFKA-7209 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-7126) Reduce number of rebalance period for large consumer groups after a topic is created

[ https://issues.apache.org/jira/browse/KAFKA-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7126: Fix Version/s: 2.1.0 2.0.0 > Reduce number of rebalance period for large consumer

[jira] [Commented] (KAFKA-4690) IllegalStateException using DeleteTopicsRequest when delete.topic.enable=false

[ https://issues.apache.org/jira/browse/KAFKA-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558608#comment-16558608 ] ASF GitHub Bot commented on KAFKA-4690: --- omkreddy closed pull request #5130: KAFKA-4690: Return new

[jira] [Resolved] (KAFKA-4690) IllegalStateException using DeleteTopicsRequest when delete.topic.enable=false

[ https://issues.apache.org/jira/browse/KAFKA-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4690. -- Resolution: Duplicate Resolving as duplicate of KAFKA-5975. > IllegalStateException using

[jira] [Commented] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558593#comment-16558593 ] Ismael Juma commented on KAFKA-5621: KAFKA-5886, which is another way of fixing the underlying

[jira] [Commented] (KAFKA-7134) KafkaLog4jAppender - Appender exceptions are propagated to caller

[ https://issues.apache.org/jira/browse/KAFKA-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558325#comment-16558325 ] Attila Sasvari commented on KAFKA-7134: --- [~venkatpotru] please note if the underlying producer

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558265#comment-16558265 ] lambdaliu commented on KAFKA-7190: -- Hello [~guozhang]. My team developed a cloud version Kafka and I am

[jira] [Resolved] (KAFKA-7208) AlterConfigsRequest with null config value throws NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Policarpio resolved KAFKA-7208. Resolution: Not A Problem Oops, realised I misunderstood how this API request works;

[jira] [Commented] (KAFKA-7134) KafkaLog4jAppender - Appender exceptions are propagated to caller

[ https://issues.apache.org/jira/browse/KAFKA-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558077#comment-16558077 ] venkata praveen commented on KAFKA-7134: This issue is about 1st one i.e : 

[jira] [Commented] (KAFKA-7134) KafkaLog4jAppender - Appender exceptions are propagated to caller

[ https://issues.apache.org/jira/browse/KAFKA-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558028#comment-16558028 ] Andras Katona commented on KAFKA-7134: -- I just realized, there are two KafkaLog4jAppender classes:

[jira] [Commented] (KAFKA-6520) When a Kafka Stream can't communicate with the server, it's Status stays RUNNING

[ https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556958#comment-16556958 ] Matthias J. Sax commented on KAFKA-6520: No worries. All good :) A KIP is a "Kafka Improvement

[jira] [Updated] (KAFKA-7208) AlterConfigsRequest with null config value throws NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Policarpio updated KAFKA-7208: --- Description: The following exception is thrown from the Kafka server when an

[jira] [Created] (KAFKA-7208) AlterConfigsRequest with null config value throws NullPointerException

Sean Policarpio created KAFKA-7208: -- Summary: AlterConfigsRequest with null config value throws NullPointerException Key: KAFKA-7208 URL: https://issues.apache.org/jira/browse/KAFKA-7208 Project: