[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=17076895#comment-17076895 ] Raman Gupta commented on KAFKA-8803: We are on 2.4.1 now, locally patched with the fix for

[jira] [Created] (KAFKA-9827) MM2 doesnt replicate data

Dmitry created KAFKA-9827: - Summary: MM2 doesnt replicate data Key: KAFKA-9827 URL: https://issues.apache.org/jira/browse/KAFKA-9827 Project: Kafka Issue Type: Bug Components: mirrormaker

[jira] [Commented] (KAFKA-9818) Flaky Test RecordCollectorTest.shouldNotThrowStreamsExceptionOnSubsequentCallIfASendFailsWithContinueExceptionHandler

[ https://issues.apache.org/jira/browse/KAFKA-9818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076890#comment-17076890 ] Matthias J. Sax commented on KAFKA-9818: This might be related to 

[jira] [Commented] (KAFKA-9819) Flaky Test StoreChangelogReaderTest#shouldNotThrowOnUnknownRevokedPartition[0]

[ https://issues.apache.org/jira/browse/KAFKA-9819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076889#comment-17076889 ] Matthias J. Sax commented on KAFKA-9819: This might be related to

[jira] [Assigned] (KAFKA-9819) Flaky Test StoreChangelogReaderTest#shouldNotThrowOnUnknownRevokedPartition[0]

[ https://issues.apache.org/jira/browse/KAFKA-9819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-9819: -- Assignee: Matthias J. Sax > Flaky Test

[jira] [Commented] (KAFKA-9818) Flaky Test RecordCollectorTest.shouldNotThrowStreamsExceptionOnSubsequentCallIfASendFailsWithContinueExceptionHandler

[ https://issues.apache.org/jira/browse/KAFKA-9818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076888#comment-17076888 ] ASF GitHub Bot commented on KAFKA-9818: --- mjsax commented on pull request #8423: KAFKA-9818: improve

[jira] [Commented] (KAFKA-8264) Flaky Test PlaintextConsumerTest#testLowMaxFetchSizeForRequestAndPartition

[ https://issues.apache.org/jira/browse/KAFKA-8264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076887#comment-17076887 ] Matthias J. Sax commented on KAFKA-8264:

[jira] [Commented] (KAFKA-7965) Flaky Test ConsumerBounceTest#testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup

[ https://issues.apache.org/jira/browse/KAFKA-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076886#comment-17076886 ] Matthias J. Sax commented on KAFKA-7965:

[jira] [Commented] (KAFKA-6145) Warm up new KS instances before migrating tasks - potentially a two phase rebalance

[ https://issues.apache.org/jira/browse/KAFKA-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076870#comment-17076870 ] ASF GitHub Bot commented on KAFKA-6145: --- ableegoldman commented on pull request #8436: KAFKA-6145:

[jira] [Updated] (KAFKA-9826) Log cleaning repeatedly picks same segment with no effect when first dirty offset is past start of active segment

[ https://issues.apache.org/jira/browse/KAFKA-9826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rodrigues updated KAFKA-9826: --- Summary: Log cleaning repeatedly picks same segment with no effect when first dirty offset

[jira] [Resolved] (KAFKA-9815) Consumer may never re-join if inconsistent metadata is received once

[ https://issues.apache.org/jira/browse/KAFKA-9815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9815. Fix Version/s: 2.4.2 2.5.0 Resolution: Fixed > Consumer may

[jira] [Commented] (KAFKA-9815) Consumer may never re-join if inconsistent metadata is received once

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

[jira] [Commented] (KAFKA-9697) ControlPlaneNetworkProcessorAvgIdlePercent is always NaN

[ https://issues.apache.org/jira/browse/KAFKA-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076763#comment-17076763 ] James Cheng commented on KAFKA-9697: Oh, no, we don't have that setup. I had assumed that the 

[jira] [Created] (KAFKA-9826) Log cleaning goes in infinite loop when first dirty offset is past start of active segment

Steve Rodrigues created KAFKA-9826: -- Summary: Log cleaning goes in infinite loop when first dirty offset is past start of active segment Key: KAFKA-9826 URL: https://issues.apache.org/jira/browse/KAFKA-9826

[jira] [Commented] (KAFKA-9753) Add task-level active-process-ratio to Streams metrics

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

[jira] [Updated] (KAFKA-9751) Admin `FindCoordinator` call should go to controller instead of ZK

[ https://issues.apache.org/jira/browse/KAFKA-9751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen updated KAFKA-9751: --- Parent: (was: KAFKA-9119) Issue Type: Improvement (was: Sub-task) > Admin

[jira] [Updated] (KAFKA-9751) Admin `FindCoordinator` call should go to controller instead of ZK

[ https://issues.apache.org/jira/browse/KAFKA-9751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen updated KAFKA-9751: --- Parent: KAFKA-9705 Issue Type: Sub-task (was: Improvement) > Admin `FindCoordinator` call

[jira] [Commented] (KAFKA-9543) Consumer offset reset after new segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076676#comment-17076676 ] Alexis Seigneurin commented on KAFKA-9543: -- We have been seeing the same issue here with Kafka

[jira] [Updated] (KAFKA-9543) Consumer offset reset after new segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Seigneurin updated KAFKA-9543: - Attachment: image-2020-04-06-17-10-32-636.png > Consumer offset reset after new segment

[jira] [Commented] (KAFKA-9438) Issue with mm2 active/active replication

[ https://issues.apache.org/jira/browse/KAFKA-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076672#comment-17076672 ] Rens Groothuijsen commented on KAFKA-9438: -- [~romanius11] Tried to replicate this issue, though

[jira] [Created] (KAFKA-9825) Kafka protocol BNF format should have some way to display tagged fields

Colin McCabe created KAFKA-9825: --- Summary: Kafka protocol BNF format should have some way to display tagged fields Key: KAFKA-9825 URL: https://issues.apache.org/jira/browse/KAFKA-9825 Project: Kafka

[jira] [Updated] (KAFKA-9825) Kafka protocol BNF format should have some way to display tagged fields

[ https://issues.apache.org/jira/browse/KAFKA-9825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe updated KAFKA-9825: Labels: newbie (was: ) > Kafka protocol BNF format should have some way to display tagged fields

[jira] [Commented] (KAFKA-9770) Caching State Store does not Close Underlying State Store When Exception is Thrown During Flushing

[ https://issues.apache.org/jira/browse/KAFKA-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076615#comment-17076615 ] John Roesler commented on KAFKA-9770: - Thanks, [~mjsax] ! > Caching State Store does not Close

[jira] [Commented] (KAFKA-9770) Caching State Store does not Close Underlying State Store When Exception is Thrown During Flushing

[ https://issues.apache.org/jira/browse/KAFKA-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076614#comment-17076614 ] Matthias J. Sax commented on KAFKA-9770: The commit was cherry-picked to 2.5 and there will be a

[jira] [Updated] (KAFKA-9770) Caching State Store does not Close Underlying State Store When Exception is Thrown During Flushing

[ https://issues.apache.org/jira/browse/KAFKA-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-9770: --- Fix Version/s: (was: 2.6.0) > Caching State Store does not Close Underlying State Store

[jira] [Commented] (KAFKA-9798) org.apache.kafka.streams.integration.QueryableStateIntegrationTest.shouldAllowConcurrentAccesses

[ https://issues.apache.org/jira/browse/KAFKA-9798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076606#comment-17076606 ] Matthias J. Sax commented on KAFKA-9798:

[jira] [Commented] (KAFKA-9697) ControlPlaneNetworkProcessorAvgIdlePercent is always NaN

[ https://issues.apache.org/jira/browse/KAFKA-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076538#comment-17076538 ] Chia-Ping Tsai commented on KAFKA-9697: --- Did you config control.plane.listener.name? If not, the

[jira] [Commented] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

[ https://issues.apache.org/jira/browse/KAFKA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076516#comment-17076516 ] Jason Gustafson commented on KAFKA-9824: [~nitay.k] Thanks for the report. From the logs, we saw

[jira] [Commented] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

[ https://issues.apache.org/jira/browse/KAFKA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076491#comment-17076491 ] Boyang Chen commented on KAFKA-9824: Thanks for reporting. Does the lost partition happen after each

[jira] [Commented] (KAFKA-3824) Docs indicate auto.commit breaks at least once delivery but that is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076359#comment-17076359 ] ASF GitHub Bot commented on KAFKA-3824: --- amanullah92 commented on pull request #8194: KAFKA-3824 |

[jira] [Updated] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

[ https://issues.apache.org/jira/browse/KAFKA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitay Kufert updated KAFKA-9824: Description: Hello, around 2 weeks ago we upgraded our Kafka clients & brokers to 2.4.1 (from

[jira] [Updated] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

[ https://issues.apache.org/jira/browse/KAFKA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitay Kufert updated KAFKA-9824: Attachment: image-2020-04-06-13-14-47-014.png > Consumer loses partition offset and resets post

[jira] [Updated] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

[ https://issues.apache.org/jira/browse/KAFKA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitay Kufert updated KAFKA-9824: Description: Hello, around 2 weeks ago we upgraded our Kafka clients & brokers to 2.4.1 (from

[jira] [Created] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

Nitay Kufert created KAFKA-9824: --- Summary: Consumer loses partition offset and resets post 2.4.1 version upgrade Key: KAFKA-9824 URL: https://issues.apache.org/jira/browse/KAFKA-9824 Project: Kafka

[jira] [Commented] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076167#comment-17076167 ] Evan Williams commented on KAFKA-4084: -- [~sql_consulting] Many thanks for that details info. Sounds

[jira] [Commented] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076124#comment-17076124 ] GEORGE LI commented on KAFKA-4084: -- [~blodsbror] If this turns out to be positive in the testing. I

[jira] [Comment Edited] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076092#comment-17076092 ] Evan Williams edited comment on KAFKA-4084 at 4/6/20, 7:35 AM: ---

[jira] [Commented] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076092#comment-17076092 ] Evan Williams commented on KAFKA-4084: -- [~sql_consulting] Thanks. Yes, I already have that logic

[jira] [Comment Edited] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076064#comment-17076064 ] Evan Williams edited comment on KAFKA-4084 at 4/6/20, 7:29 AM: --- Much

[jira] [Commented] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076089#comment-17076089 ] GEORGE LI commented on KAFKA-4084: -- [~blodsbror] I think it's still ok to set

[jira] [Comment Edited] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076064#comment-17076064 ] Evan Williams edited comment on KAFKA-4084 at 4/6/20, 7:24 AM: --- Much

[jira] [Comment Edited] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076006#comment-17076006 ] GEORGE LI edited comment on KAFKA-4084 at 4/6/20, 7:13 AM: --- [~blodsbror] Have

[jira] [Commented] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076064#comment-17076064 ] Evan Williams commented on KAFKA-4084: -- Much appreciated [~sql_consulting].  I've requested access