[jira] [Commented] (KAFKA-5593) Kafka streams not re-balancing when 3 consumer streams are there

[ https://issues.apache.org/jira/browse/KAFKA-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091135#comment-16091135 ] Yogesh BG commented on KAFKA-5593: -- Hey thanks fro pointing down that. Yes you are correct. I changed the

[jira] [Commented] (KAFKA-2527) System Test for Quotas in Ducktape

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

[jira] [Resolved] (KAFKA-5605) Multiple KStreams being created on application startup are not processing

[ https://issues.apache.org/jira/browse/KAFKA-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Connie Chen resolved KAFKA-5605. Resolution: Not A Problem > Multiple KStreams being created on application startup are not

[jira] [Commented] (KAFKA-5605) Multiple KStreams being created on application startup are not processing

[ https://issues.apache.org/jira/browse/KAFKA-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090812#comment-16090812 ] Connie Chen commented on KAFKA-5605: [~mjsax] helped me fix the issue. It appears I was sharing

[jira] [Commented] (KAFKA-5587) Processor got uncaught exception: NullPointerException

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

[jira] [Updated] (KAFKA-5605) Multiple KStreams being created on application startup are not processing

[ https://issues.apache.org/jira/browse/KAFKA-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Connie Chen updated KAFKA-5605: --- Description: This is an issue filed in response to this slack discussion

[jira] [Updated] (KAFKA-5605) Multiple KStreams being created on application startup are not processing

[ https://issues.apache.org/jira/browse/KAFKA-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Connie Chen updated KAFKA-5605: --- Summary: Multiple KStreams being created on application startup are not processing (was: KStream

[jira] [Created] (KAFKA-5605) KStream being created on application startup is not processing

Connie Chen created KAFKA-5605: -- Summary: KStream being created on application startup is not processing Key: KAFKA-5605 URL: https://issues.apache.org/jira/browse/KAFKA-5605 Project: Kafka

[jira] [Created] (KAFKA-5604) All producer methods should raise `ProducerFencedException` after the first time.

Apurva Mehta created KAFKA-5604: --- Summary: All producer methods should raise `ProducerFencedException` after the first time. Key: KAFKA-5604 URL: https://issues.apache.org/jira/browse/KAFKA-5604

[jira] [Created] (KAFKA-5603) Streams should not abort transaction when closing zombie task

Matthias J. Sax created KAFKA-5603: -- Summary: Streams should not abort transaction when closing zombie task Key: KAFKA-5603 URL: https://issues.apache.org/jira/browse/KAFKA-5603 Project: Kafka

[jira] [Commented] (KAFKA-5600) GroupMetadataManager doesn't read offsets of segmented logs correctly

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

[jira] [Commented] (KAFKA-5595) Illegal state in SocketServer; attempt to send with another send in progress

[ https://issues.apache.org/jira/browse/KAFKA-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090205#comment-16090205 ] Jason Gustafson commented on KAFKA-5595: Ensuring connectionId uniqueness is a nice improvement,

[jira] [Resolved] (KAFKA-5579) SchemaBuilder.type(Schema.Type) should not allow null.

[ https://issues.apache.org/jira/browse/KAFKA-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5579. -- Resolution: Fixed Fix Version/s: 0.11.1.0 Issue resolved by pull request

[jira] [Commented] (KAFKA-5545) Kafka Stream not able to successfully restart over new broker ip

[ https://issues.apache.org/jira/browse/KAFKA-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090111#comment-16090111 ] Guozhang Wang commented on KAFKA-5545: -- Hello [~yogeshbelur] sorry for the late reply. I think I

[jira] [Commented] (KAFKA-5602) Add --custom-ducktape flag to ducker-ak

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

[jira] [Created] (KAFKA-5602) Add --custom-ducktape flag to ducker-ak

Colin P. McCabe created KAFKA-5602: -- Summary: Add --custom-ducktape flag to ducker-ak Key: KAFKA-5602 URL: https://issues.apache.org/jira/browse/KAFKA-5602 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4794) Add access to OffsetStorageReader from SourceConnector

[ https://issues.apache.org/jira/browse/KAFKA-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090034#comment-16090034 ] Oleg Kuznetsov commented on KAFKA-4794: --- [~fhussonnois] I meant who could give it? > Add access to

[jira] [Commented] (KAFKA-4794) Add access to OffsetStorageReader from SourceConnector

[ https://issues.apache.org/jira/browse/KAFKA-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090023#comment-16090023 ] Florian Hussonnois commented on KAFKA-4794: --- [~olkuznsmith] The KIP is created

[jira] [Commented] (KAFKA-1694) KIP-4: Command line and centralized operations

[ https://issues.apache.org/jira/browse/KAFKA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090014#comment-16090014 ] Stevo Slavic commented on KAFKA-1694: - Here's one use case: with auto topic creation disabled, when

[jira] [Created] (KAFKA-5601) Refactor ReassignPartitionsCommand to use AdminClient

Tom Bentley created KAFKA-5601: -- Summary: Refactor ReassignPartitionsCommand to use AdminClient Key: KAFKA-5601 URL: https://issues.apache.org/jira/browse/KAFKA-5601 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-5274) Review and improve AdminClient Javadoc for the first release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089993#comment-16089993 ] Stevo Slavic commented on KAFKA-5274: - Sorry for late feedback, missed that this client was being

[jira] [Commented] (KAFKA-5588) ConsoleConsumer : uselss --new-consumer option

[ https://issues.apache.org/jira/browse/KAFKA-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089819#comment-16089819 ] Paolo Patierno commented on KAFKA-5588: --- I have just written the

[jira] [Commented] (KAFKA-1694) KIP-4: Command line and centralized operations

[ https://issues.apache.org/jira/browse/KAFKA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089810#comment-16089810 ] Ismael Juma commented on KAFKA-1694: [~sslavic], `AdminUtils` is communicating with ZooKeeper

[jira] [Commented] (KAFKA-1694) KIP-4: Command line and centralized operations

[ https://issues.apache.org/jira/browse/KAFKA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089801#comment-16089801 ] Stevo Slavic commented on KAFKA-1694: - Thanks for providing Java AdminClient. While migrating from

[jira] [Commented] (KAFKA-5600) GroupMetadataManager doesn't read offsets of segmented logs correctly

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

[jira] [Updated] (KAFKA-5600) GroupMetadataManager doesn't read offsets of segmented logs correctly

[ https://issues.apache.org/jira/browse/KAFKA-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5600: --- Labels: reliability (was: ) > GroupMetadataManager doesn't read offsets of segmented logs correctly

[jira] [Updated] (KAFKA-5600) GroupMetadataManager doesn't read offsets of segmented logs correctly

[ https://issues.apache.org/jira/browse/KAFKA-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5600: --- Fix Version/s: 0.11.0.1 > GroupMetadataManager doesn't read offsets of segmented logs correctly >

[jira] [Updated] (KAFKA-5600) GroupMetadataManager doesn't read offsets of segmented logs correctly

[ https://issues.apache.org/jira/browse/KAFKA-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Burkhardt updated KAFKA-5600: - Description: After long investigation we found a Problem in Kafka. When a __consumer_offsets

[jira] [Updated] (KAFKA-5600) GroupMetadataManager doesn't read Offsets of segmented log correctly

[ https://issues.apache.org/jira/browse/KAFKA-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Burkhardt updated KAFKA-5600: - Description: After long investigation we found a Problem in Kafka. When a __consumer_offsets

[jira] [Updated] (KAFKA-5600) GroupMetadataManager doesn't read Offsets of segmented log correctly

[ https://issues.apache.org/jira/browse/KAFKA-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Burkhardt updated KAFKA-5600: - Description: After long investigation we found a Problem in Kafka. When a __consumer_offsets

[jira] [Updated] (KAFKA-5600) GroupMetadataManager doesn't read Offsets of segmented log correctly

[ https://issues.apache.org/jira/browse/KAFKA-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Burkhardt updated KAFKA-5600: - Description: After long investigation we found a Problem in Kafka. When a __consumer_offsets

[jira] [Updated] (KAFKA-5600) GroupMetadataManager doesn't read Offsets of segmented log correctly

[ https://issues.apache.org/jira/browse/KAFKA-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Burkhardt updated KAFKA-5600: - Description: After long investigation we found a Problem in Kafka. When a __consumer_offsets

[jira] [Resolved] (KAFKA-5585) Failover in a replicated Cluster does not work

[ https://issues.apache.org/jira/browse/KAFKA-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Bayer resolved KAFKA-5585. - Resolution: Cannot Reproduce After setting up everything from scratch I was not able to reproduce

[jira] [Commented] (KAFKA-5585) Failover in a replicated Cluster does not work

[ https://issues.apache.org/jira/browse/KAFKA-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089709#comment-16089709 ] Thomas Bayer commented on KAFKA-5585: - After repeating the whole setup from scratch it worked with

[jira] [Updated] (KAFKA-5600) GroupMetadataManager doesn't read Offsets of segmented log correctly

[ https://issues.apache.org/jira/browse/KAFKA-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Burkhardt updated KAFKA-5600: - Description: After long investigation we found a Problem in Kafka. When a __consumer_offsets

[jira] [Commented] (KAFKA-5599) ConsoleConsumer : --new-consumer option as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089684#comment-16089684 ] Ismael Juma commented on KAFKA-5599: For background, there was a time when "--new-consumer" was

[jira] [Comment Edited] (KAFKA-5599) ConsoleConsumer : --new-consumer option as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089684#comment-16089684 ] Ismael Juma edited comment on KAFKA-5599 at 7/17/17 11:35 AM: -- For

[jira] [Commented] (KAFKA-5588) ConsumerConsole : uselss --new-consumer option

[ https://issues.apache.org/jira/browse/KAFKA-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089621#comment-16089621 ] Ismael Juma commented on KAFKA-5588: That's right [~vahid], we generally need a KIP for changes with a

[jira] [Updated] (KAFKA-5547) Return topic authorization failed if no topic describe access

[ https://issues.apache.org/jira/browse/KAFKA-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5547: --- Labels: security usability (was: ) > Return topic authorization failed if no topic describe access >

[jira] [Commented] (KAFKA-5547) Return topic authorization failed if no topic describe access

[ https://issues.apache.org/jira/browse/KAFKA-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089617#comment-16089617 ] Ismael Juma commented on KAFKA-5547: [~hachikuji], it seems like that could work. As long as we're

[jira] [Commented] (KAFKA-3856) Cleanup Kafka Streams builder API

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