[jira] [Commented] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062286#comment-17062286 ] Raman Gupta commented on KAFKA-8803: [~guozhang] I plan on upgrading to 2.4.1 (from 2.3.0) within the

[jira] [Updated] (KAFKA-9568) Kstreams APPLICATION_SERVER_CONFIG is not updated with static membership

[ https://issues.apache.org/jira/browse/KAFKA-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sophie Blee-Goldman updated KAFKA-9568: --- Affects Version/s: 2.5.0 > Kstreams APPLICATION_SERVER_CONFIG is not updated with

[jira] [Updated] (KAFKA-9568) Kstreams APPLICATION_SERVER_CONFIG is not updated with static membership

[ https://issues.apache.org/jira/browse/KAFKA-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sophie Blee-Goldman updated KAFKA-9568: --- Fix Version/s: 2.6.0 > Kstreams APPLICATION_SERVER_CONFIG is not updated with static

[jira] [Resolved] (KAFKA-9636) Simple join of two KTables fails

[ https://issues.apache.org/jira/browse/KAFKA-9636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-9636. - Resolution: Not A Bug Closing this ticket as "not a bug" because the test failure turned out to

[jira] [Commented] (KAFKA-9636) Simple join of two KTables fails

[ https://issues.apache.org/jira/browse/KAFKA-9636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062223#comment-17062223 ] John Roesler commented on KAFKA-9636: - NP, and thanks again for your assistance and very clear and

[jira] [Commented] (KAFKA-9568) Kstreams APPLICATION_SERVER_CONFIG is not updated with static membership

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

[jira] [Commented] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062200#comment-17062200 ] Guozhang Wang commented on KAFKA-8803: -- [~rocketraman] Here's my current investigation described

[jira] [Commented] (KAFKA-8858) Kafka Streams - Failed to Rebalance Error and stream consumer stuck for some reason

[ https://issues.apache.org/jira/browse/KAFKA-8858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062181#comment-17062181 ] Sophie Blee-Goldman commented on KAFKA-8858: I thought they were different exceptions due to

[jira] [Commented] (KAFKA-8858) Kafka Streams - Failed to Rebalance Error and stream consumer stuck for some reason

[ https://issues.apache.org/jira/browse/KAFKA-8858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062178#comment-17062178 ] Guozhang Wang commented on KAFKA-8858: -- [~ableegoldman] I'm not sure I followed your explanation

[jira] [Commented] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062177#comment-17062177 ] Guozhang Wang commented on KAFKA-8803: -- [~ableegoldman] I think 8858 and 8803 are referring to the

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

[ https://issues.apache.org/jira/browse/KAFKA-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5604. -- Fix Version/s: 2.3.0 Assignee: Guozhang Wang (was: Apurva Mehta) Resolution:

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

[ https://issues.apache.org/jira/browse/KAFKA-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062064#comment-17062064 ] Guozhang Wang commented on KAFKA-5604: -- Verified that I've fixed the producer as in

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

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

[jira] [Resolved] (KAFKA-9656) TxnOffsetCommit should not return COORDINATOR_LOADING error for old request versions

[ https://issues.apache.org/jira/browse/KAFKA-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9656. Fix Version/s: 2.6.0 Resolution: Fixed > TxnOffsetCommit should not return

[jira] [Commented] (KAFKA-9656) TxnOffsetCommit should not return COORDINATOR_LOADING error for old request versions

[ https://issues.apache.org/jira/browse/KAFKA-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062011#comment-17062011 ] ASF GitHub Bot commented on KAFKA-9656: --- hachikuji commented on pull request #8253: KAFKA-9656:

[jira] [Closed] (KAFKA-9625) Unable to Describe broker configurations that have been set via IncrementalAlterConfigs

[ https://issues.apache.org/jira/browse/KAFKA-9625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjana Kaundinya closed KAFKA-9625. > Unable to Describe broker configurations that have been set via > IncrementalAlterConfigs >

[jira] [Closed] (KAFKA-9047) AdminClient group operations may not respect backoff

[ https://issues.apache.org/jira/browse/KAFKA-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjana Kaundinya closed KAFKA-9047. > AdminClient group operations may not respect backoff >

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

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

[jira] [Commented] (KAFKA-9047) AdminClient group operations may not respect backoff

[ https://issues.apache.org/jira/browse/KAFKA-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062009#comment-17062009 ] ASF GitHub Bot commented on KAFKA-9047: --- hachikuji commented on pull request #8161: KAFKA-9047:

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

[ https://issues.apache.org/jira/browse/KAFKA-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062006#comment-17062006 ] Guozhang Wang commented on KAFKA-5604: -- [~iamabug] There are some context missing from this comment:

[jira] [Reopened] (KAFKA-8122) Flaky Test EosIntegrationTest#shouldNotViolateEosIfOneTaskFailsWithState

[ https://issues.apache.org/jira/browse/KAFKA-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen reopened KAFKA-8122: Assignee: (was: Matthias J. Sax) > Flaky Test

[jira] [Commented] (KAFKA-8122) Flaky Test EosIntegrationTest#shouldNotViolateEosIfOneTaskFailsWithState

[ https://issues.apache.org/jira/browse/KAFKA-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062005#comment-17062005 ] Boyang Chen commented on KAFKA-8122: Failed again 

[jira] [Updated] (KAFKA-9732) Kafka Foreign-Key Joiner has unexpected default value used when a table is created via a stream+groupByKey+reduce

[ https://issues.apache.org/jira/browse/KAFKA-9732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-9732: --- Component/s: streams > Kafka Foreign-Key Joiner has unexpected default value used when a

[jira] [Updated] (KAFKA-9732) Kafka Foreign-Key Joiner has unexpected default value used when a table is created via a stream+groupByKey+reduce

[ https://issues.apache.org/jira/browse/KAFKA-9732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-9732: --- Affects Version/s: (was: 2.4.0) > Kafka Foreign-Key Joiner has unexpected default value

[jira] [Commented] (KAFKA-9432) Replace DescribeConfigs request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-9432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061946#comment-17061946 ] ASF GitHub Bot commented on KAFKA-9432: --- tombentley commented on pull request #8312: KAFKA-9432

[jira] [Comment Edited] (KAFKA-9732) Kafka Foreign-Key Joiner has unexpected default value used when a table is created via a stream+groupByKey+reduce

[ https://issues.apache.org/jira/browse/KAFKA-9732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061921#comment-17061921 ] Adam Bellemare edited comment on KAFKA-9732 at 3/18/20, 5:14 PM: -

[jira] [Commented] (KAFKA-9732) Kafka Foreign-Key Joiner has unexpected default value used when a table is created via a stream+groupByKey+reduce

[ https://issues.apache.org/jira/browse/KAFKA-9732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061921#comment-17061921 ] Adam Bellemare commented on KAFKA-9732: --- [~vvcephei] Hey John Not sure if this is a known-issue

[jira] [Updated] (KAFKA-9733) Consider addition of leader quorum in replication model

[ https://issues.apache.org/jira/browse/KAFKA-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-9733: -- Description: Kafka's current replication model (with its single leader and several followers) is

[jira] [Updated] (KAFKA-9733) Consider addition of leader quorum in replication model

[ https://issues.apache.org/jira/browse/KAFKA-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-9733: -- Description: Kafka's current replication model (with its single leader and several followers) is

[jira] [Updated] (KAFKA-9733) Consider addition of leader quorum in replication model

[ https://issues.apache.org/jira/browse/KAFKA-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-9733: -- Description: Kafka's current replication model (with its single leader and several followers) is

[jira] [Updated] (KAFKA-9733) Consider addition of leader quorum in replication model

[ https://issues.apache.org/jira/browse/KAFKA-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-9733: -- Description: Kafka's current replication model (with its single leader and several followers) is

[jira] [Updated] (KAFKA-9730) add tag "partition" to BrokerTopicMetrics so as to observe the partition metrics on the same broker

[ https://issues.apache.org/jira/browse/KAFKA-9730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated KAFKA-9730: -- Labels: needs-kip (was: ) > add tag "partition" to BrokerTopicMetrics so as to observe the

[jira] [Updated] (KAFKA-9733) Consider addition of leader quorum in replication model

[ https://issues.apache.org/jira/browse/KAFKA-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-9733: -- Description: Kafka's current replication model (with its single leader and several followers) is

[jira] [Updated] (KAFKA-9733) Consider addition of leader quorum in replication model

[ https://issues.apache.org/jira/browse/KAFKA-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-9733: -- Summary: Consider addition of leader quorum in replication model (was: Consider addition of leader

[jira] [Updated] (KAFKA-9733) Consider addition of leader partition quorum

[ https://issues.apache.org/jira/browse/KAFKA-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-9733: -- Description: Note: Description still not finished. Still not sure if this is needed. Kafka's current

[jira] [Updated] (KAFKA-9733) Consider addition of leader partition quorum

[ https://issues.apache.org/jira/browse/KAFKA-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-9733: -- Summary: Consider addition of leader partition quorum (was: Consider addition to Kafka's replication

[jira] [Updated] (KAFKA-9733) Consider addition to Kafka's replication model

[ https://issues.apache.org/jira/browse/KAFKA-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-9733: -- Description: Note: Description still not finished. Still not sure if this is needed. This feature I'm

[jira] [Updated] (KAFKA-9733) Consider addition to Kafka's replication model

[ https://issues.apache.org/jira/browse/KAFKA-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-9733: -- Description: Note: Description still not finished. This feature I'm proposing might not offer too

[jira] [Created] (KAFKA-9733) Consider addition to Kafka's replication model

Richard Yu created KAFKA-9733: - Summary: Consider addition to Kafka's replication model Key: KAFKA-9733 URL: https://issues.apache.org/jira/browse/KAFKA-9733 Project: Kafka Issue Type: New

[jira] [Commented] (KAFKA-9500) Foreign-Key Join creates an invalid topology

[ https://issues.apache.org/jira/browse/KAFKA-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061804#comment-17061804 ] Adam Bellemare commented on KAFKA-9500: --- [~vvcephei] Hey John - I ran across this while trying to

[jira] [Created] (KAFKA-9732) Kafka Foreign-Key Joiner has unexpected default value used when a table is created via a stream+groupByKey+reduce

Adam Bellemare created KAFKA-9732: - Summary: Kafka Foreign-Key Joiner has unexpected default value used when a table is created via a stream+groupByKey+reduce Key: KAFKA-9732 URL:

[jira] [Resolved] (KAFKA-9404) Use ArrayList instead of LinkedList in Sensor Class

[ https://issues.apache.org/jira/browse/KAFKA-9404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9404. Fix Version/s: 2.6.0 Resolution: Fixed > Use ArrayList instead of LinkedList in Sensor

[jira] [Commented] (KAFKA-9404) Use ArrayList instead of LinkedList in Sensor Class

[ https://issues.apache.org/jira/browse/KAFKA-9404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061731#comment-17061731 ] ASF GitHub Bot commented on KAFKA-9404: --- ijuma commented on pull request #7936: KAFKA-9404: Use

[jira] [Commented] (KAFKA-9066) Kafka Connect JMX : source & sink task metrics missing for tasks in failed state

[ https://issues.apache.org/jira/browse/KAFKA-9066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061693#comment-17061693 ] Javier Holguera commented on KAFKA-9066: Dealing with this problem as well. Seems to be related

[jira] [Commented] (KAFKA-9434) Replace AlterReplicaLogDirs request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-9434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061632#comment-17061632 ] ASF GitHub Bot commented on KAFKA-9434: --- tombentley commented on pull request #8311: KAFKA-9434:

[jira] [Updated] (KAFKA-9590) Add configuration to limit number of partitions per broker

[ https://issues.apache.org/jira/browse/KAFKA-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokul Ramanan Subramanian updated KAFKA-9590: - Priority: Major (was: Minor) > Add configuration to limit number of

[jira] [Updated] (KAFKA-9590) Add configuration to limit number of partitions per broker

[ https://issues.apache.org/jira/browse/KAFKA-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokul Ramanan Subramanian updated KAFKA-9590: - Description: Tracks 

[jira] [Updated] (KAFKA-9590) Add configuration to limit number of partitions per broker

[ https://issues.apache.org/jira/browse/KAFKA-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokul Ramanan Subramanian updated KAFKA-9590: - Summary: Add configuration to limit number of partitions per broker

[jira] [Updated] (KAFKA-9590) Add configuration to limit number of topic partitions

[ https://issues.apache.org/jira/browse/KAFKA-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokul Ramanan Subramanian updated KAFKA-9590: - Summary: Add configuration to limit number of topic partitions (was: Add

[jira] [Commented] (KAFKA-9625) Unable to Describe broker configurations that have been set via IncrementalAlterConfigs

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