[jira] [Commented] (KAFKA-6652) The controller should log failed attempts to transition a replica to OfflineReplica state if there is no leadership info

[ https://issues.apache.org/jira/browse/KAFKA-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412377#comment-16412377 ] ASF GitHub Bot commented on KAFKA-6652: --- gitlw closed pull request #4769: KAFKA-6652

[jira] [Commented] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412346#comment-16412346 ] Brett Rann commented on KAFKA-5413: --- Is this the same issue as was reported here? https

[jira] [Commented] (KAFKA-6612) Added logic to prevent increasing partition counts during topic deletion

[ https://issues.apache.org/jira/browse/KAFKA-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412336#comment-16412336 ] ASF GitHub Bot commented on KAFKA-6612: --- becketqin closed pull request #4666: KAFKA-

[jira] [Commented] (KAFKA-6652) The controller should log failed attempts to transition a replica to OfflineReplica state if there is no leadership info

[ https://issues.apache.org/jira/browse/KAFKA-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412305#comment-16412305 ] ASF GitHub Bot commented on KAFKA-6652: --- gitlw opened a new pull request #4769: KAFK

[jira] [Updated] (KAFKA-6652) The controller should log failed attempts to transition a replica to OfflineReplica state if there is no leadership info

[ https://issues.apache.org/jira/browse/KAFKA-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Wang updated KAFKA-6652: -- Description: In certain conditions, the controller's attempt to transition a replica to OfflineReplica s

[jira] [Updated] (KAFKA-6652) The controller should log failed attempts to transition a replica to OfflineReplica state if there is no leadership info

[ https://issues.apache.org/jira/browse/KAFKA-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Wang updated KAFKA-6652: -- Summary: The controller should log failed attempts to transition a replica to OfflineReplica state if th

[jira] [Commented] (KAFKA-6054) ERROR "SubscriptionInfo - unable to decode subscription data: version=2" when upgrading from 0.10.0.0 to 0.10.2.1

[ https://issues.apache.org/jira/browse/KAFKA-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412266#comment-16412266 ] ASF GitHub Bot commented on KAFKA-6054: --- mjsax opened a new pull request #4768: KAF

[jira] [Updated] (KAFKA-5965) Remove Deprecated AdminClient from Streams Resetter Tool

[ https://issues.apache.org/jira/browse/KAFKA-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5965: - Labels: newbie (was: ) > Remove Deprecated AdminClient from Streams Resetter Tool > -

[jira] [Assigned] (KAFKA-4996) Fix findbugs multithreaded correctness warnings for streams

[ https://issues.apache.org/jira/browse/KAFKA-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-4996: Assignee: (was: Amit Daga) > Fix findbugs multithreaded correctness warnings for stream

[jira] [Assigned] (KAFKA-6437) Streams does not warn about missing input topics, but hangs

[ https://issues.apache.org/jira/browse/KAFKA-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariam John reassigned KAFKA-6437: -- Assignee: Mariam John > Streams does not warn about missing input topics, but hangs > -

[jira] [Commented] (KAFKA-6437) Streams does not warn about missing input topics, but hangs

[ https://issues.apache.org/jira/browse/KAFKA-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411910#comment-16411910 ] Mariam John commented on KAFKA-6437: I will do that [~mjsax]. I agree that a WARN mess

[jira] [Commented] (KAFKA-6437) Streams does not warn about missing input topics, but hangs

[ https://issues.apache.org/jira/browse/KAFKA-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411873#comment-16411873 ] Matthias J. Sax commented on KAFKA-6437: Sounds good to me. Feel free to work on t

[jira] [Commented] (KAFKA-6699) When one of two Kafka nodes are dead, streaming API cannot handle messaging

[ https://issues.apache.org/jira/browse/KAFKA-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411758#comment-16411758 ] Matthias J. Sax commented on KAFKA-6699: If replication factor is 2, can you even

[jira] [Resolved] (KAFKA-6676) System tests do not handle ZK chroot properly with SCRAM

[ https://issues.apache.org/jira/browse/KAFKA-6676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6676. -- Resolution: Fixed Fix Version/s: 1.1.0 > System tests do not handle ZK chroot properly with SCRAM

[jira] [Resolved] (KAFKA-6680) Fix config initialization in DynamicBrokerConfig

[ https://issues.apache.org/jira/browse/KAFKA-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6680. -- Resolution: Fixed Fix Version/s: (was: 1.2.0) 1.1.0 > Fix config initializ

[jira] [Updated] (KAFKA-4840) There are still cases where producer buffer pool will not remove waiters.

[ https://issues.apache.org/jira/browse/KAFKA-4840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Olson updated KAFKA-4840: Summary: There are still cases where producer buffer pool will not remove waiters. (was: There are

[jira] [Resolved] (KAFKA-6703) MirrorMaker cannot make progress when any matched topic from a whitelist regexp has -1 leader

[ https://issues.apache.org/jira/browse/KAFKA-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Sasvari resolved KAFKA-6703. --- Resolution: Not A Bug It turned out I forgot to set proper replication factor for {{__consume

[jira] [Commented] (KAFKA-6699) When one of two Kafka nodes are dead, streaming API cannot handle messaging

[ https://issues.apache.org/jira/browse/KAFKA-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411602#comment-16411602 ] Seweryn Habdank-Wojewodzki commented on KAFKA-6699: --- [~asasvari] Topic:_

[jira] [Updated] (KAFKA-6708) Review Exception messages with regards to Serde Useage

[ https://issues.apache.org/jira/browse/KAFKA-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-6708: --- Labels: newbie, (was: ) > Review Exception messages with regards to Serde Useage > --

[jira] [Updated] (KAFKA-6708) Review Exception messages with regards to Serde Useage

[ https://issues.apache.org/jira/browse/KAFKA-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-6708: --- Description: Error messages when not including Serdes required other than the provided default ones sh

[jira] [Updated] (KAFKA-6708) Review Exception messages with regards to Serde Useage

[ https://issues.apache.org/jira/browse/KAFKA-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-6708: --- Description: Error messages when not including Serdes required other than the provided default ones sh

[jira] [Updated] (KAFKA-6708) Review Exception messages with regards to Serde Useage

[ https://issues.apache.org/jira/browse/KAFKA-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-6708: --- Summary: Review Exception messages with regards to Serde Useage (was: Review JavaDocs, Documentation

[jira] [Updated] (KAFKA-6708) Review JavaDocs, Documentation and Exception messages with regards to Serde Useage

[ https://issues.apache.org/jira/browse/KAFKA-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-6708: --- Summary: Review JavaDocs, Documentation and Exception messages with regards to Serde Useage (was: Re

[jira] [Updated] (KAFKA-6708) Review JavaDocs and Documentation with regards to Serde Useage

[ https://issues.apache.org/jira/browse/KAFKA-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-6708: --- Description: This could also include updating the error messages to be more specific vs. just a {{Clas

[jira] [Created] (KAFKA-6708) Review JavaDocs and Documentation with regards to Serde Useage

Bill Bejeck created KAFKA-6708: -- Summary: Review JavaDocs and Documentation with regards to Serde Useage Key: KAFKA-6708 URL: https://issues.apache.org/jira/browse/KAFKA-6708 Project: Kafka Iss

[jira] [Commented] (KAFKA-6699) When one of two Kafka nodes are dead, streaming API cannot handle messaging

[ https://issues.apache.org/jira/browse/KAFKA-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411454#comment-16411454 ] Attila Sasvari commented on KAFKA-6699: --- [~habdank] just a quick question: is the re

[jira] [Commented] (KAFKA-6474) Rewrite test to use new public TopologyTestDriver

[ https://issues.apache.org/jira/browse/KAFKA-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411288#comment-16411288 ] Filipe Agapito commented on KAFKA-6474: --- Hi John. Great, I'm glad I could help. I ha

[jira] [Comment Edited] (KAFKA-6699) When one of two Kafka nodes are dead, streaming API cannot handle messaging

[ https://issues.apache.org/jira/browse/KAFKA-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411274#comment-16411274 ] Seweryn Habdank-Wojewodzki edited comment on KAFKA-6699 at 3/23/18 11:54 AM: ---

[jira] [Commented] (KAFKA-6699) When one of two Kafka nodes are dead, streaming API cannot handle messaging

[ https://issues.apache.org/jira/browse/KAFKA-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411274#comment-16411274 ] Seweryn Habdank-Wojewodzki commented on KAFKA-6699: --- [~astubbs]Replicati

[jira] [Commented] (KAFKA-6699) When one of two Kafka nodes are dead, streaming API cannot handle messaging

[ https://issues.apache.org/jira/browse/KAFKA-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411222#comment-16411222 ] Attila Sasvari commented on KAFKA-6699: --- [~habdank] have you tried to specify a diff

[jira] [Commented] (KAFKA-1614) Partition log directory name and segments information exposed via JMX

[ https://issues.apache.org/jira/browse/KAFKA-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411215#comment-16411215 ] Carlos Manuel Pacheco SOARES commented on KAFKA-1614: - Hello All, Has

[jira] [Commented] (KAFKA-6685) Connect deserialization log message should distinguish key from value

[ https://issues.apache.org/jira/browse/KAFKA-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411201#comment-16411201 ] ASF GitHub Bot commented on KAFKA-6685: --- jadireddi opened a new pull request #4765:

[jira] [Commented] (KAFKA-6707) The default value for config of Type.LONG should be *L

[ https://issues.apache.org/jira/browse/KAFKA-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411043#comment-16411043 ] ASF GitHub Bot commented on KAFKA-6707: --- hejiefang opened a new pull request #4762:

[jira] [Updated] (KAFKA-6707) The default value for config of Type.LONG should be *L

[ https://issues.apache.org/jira/browse/KAFKA-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JieFang.He updated KAFKA-6707: -- Summary: The default value for config of Type.LONG should be *L (was: The value of Type.LONG should be

[jira] [Updated] (KAFKA-6707) The value of Type.LONG should be *L

[ https://issues.apache.org/jira/browse/KAFKA-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JieFang.He updated KAFKA-6707: -- Description: h1. The default value for config of Type.LONG should be *L (was: h1. The value of Type.LON

[jira] [Updated] (KAFKA-6707) The value of Type.LONG should be *L

[ https://issues.apache.org/jira/browse/KAFKA-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JieFang.He updated KAFKA-6707: -- Description: h1. The value of Type.LONG should be *L > The value of Type.LONG should be *L > ---

[jira] [Created] (KAFKA-6707) The value of Type.LONG should be *L

JieFang.He created KAFKA-6707: - Summary: The value of Type.LONG should be *L Key: KAFKA-6707 URL: https://issues.apache.org/jira/browse/KAFKA-6707 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-3370) Add options to auto.offset.reset to reset offsets upon initialization only

[ https://issues.apache.org/jira/browse/KAFKA-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410952#comment-16410952 ] Benson Hon commented on KAFKA-3370: --- KafkaUtils.fixKafkaParams() force auto.offset.reset

[jira] [Commented] (KAFKA-6437) Streams does not warn about missing input topics, but hangs

[ https://issues.apache.org/jira/browse/KAFKA-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410940#comment-16410940 ] Chris Schwarzfischer commented on KAFKA-6437: - Yes, I think, the current behav

[jira] [Commented] (KAFKA-6706) NETWORK_EXCEPTION and REQUEST_TIMED_OUT in mirrormaker producer after 1.0 broker upgrade

[ https://issues.apache.org/jira/browse/KAFKA-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410938#comment-16410938 ] abel-sun commented on KAFKA-6706: - If you haven't please check KIP-91,The hope can help yo

[jira] [Created] (KAFKA-6706) NETWORK_EXCEPTION and REQUEST_TIMED_OUT in mirrormaker producer after 1.0 broker upgrade

Di Shang created KAFKA-6706: --- Summary: NETWORK_EXCEPTION and REQUEST_TIMED_OUT in mirrormaker producer after 1.0 broker upgrade Key: KAFKA-6706 URL: https://issues.apache.org/jira/browse/KAFKA-6706 Project:

[jira] [Updated] (KAFKA-6702) Wrong className in LoggerFactory.getLogger method

[ https://issues.apache.org/jira/browse/KAFKA-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JieFang.He updated KAFKA-6702: -- Affects Version/s: 1.0.1 > Wrong className in LoggerFactory.getLogger method > -

[jira] [Updated] (KAFKA-6705) producer.send() should not block due to metadata not available

[ https://issues.apache.org/jira/browse/KAFKA-6705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6705: Summary: producer.send() should not block due to metadata not available (was: producer.send() should be non