[jira] [Commented] (KAFKA-9013) Flaky Test MirrorConnectorsIntegrationTest#testReplication

[ https://issues.apache.org/jira/browse/KAFKA-9013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105958#comment-17105958 ] Sophie Blee-Goldman commented on KAFKA-9013:

[jira] [Commented] (KAFKA-9977) Kafka Connect Task level error metrics exposed via JMX not removed on connector delete

[ https://issues.apache.org/jira/browse/KAFKA-9977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105956#comment-17105956 ] Chris Egerton commented on KAFKA-9977: -- Thanks [~tharindu]. It looks like this is happening because

[jira] [Commented] (KAFKA-9897) Flaky Test StoreQueryIntegrationTest#shouldQuerySpecificActivePartitionStores

[ https://issues.apache.org/jira/browse/KAFKA-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105954#comment-17105954 ] Guozhang Wang commented on KAFKA-9897: -- I'd say "yes" (biased of course :) > Flaky Test

[jira] [Commented] (KAFKA-9897) Flaky Test StoreQueryIntegrationTest#shouldQuerySpecificActivePartitionStores

[ https://issues.apache.org/jira/browse/KAFKA-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105950#comment-17105950 ] Sophie Blee-Goldman commented on KAFKA-9897: [~guozhang] recently improved the integration

[jira] [Commented] (KAFKA-9982) [kafka-connect] Source connector does not guarantee at least once delivery

[ https://issues.apache.org/jira/browse/KAFKA-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105942#comment-17105942 ] Chris Egerton commented on KAFKA-9982: -- The producers the framework uses to write data from source

[jira] [Created] (KAFKA-9985) Sink connector may exhaust broker when writing in DLQ

Mario Molina created KAFKA-9985: --- Summary: Sink connector may exhaust broker when writing in DLQ Key: KAFKA-9985 URL: https://issues.apache.org/jira/browse/KAFKA-9985 Project: Kafka Issue

[jira] [Created] (KAFKA-9984) Should fail the subscription when pattern is empty

Boyang Chen created KAFKA-9984: -- Summary: Should fail the subscription when pattern is empty Key: KAFKA-9984 URL: https://issues.apache.org/jira/browse/KAFKA-9984 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-9983) Add end-to-end latency metrics to Streams

Sophie Blee-Goldman created KAFKA-9983: -- Summary: Add end-to-end latency metrics to Streams Key: KAFKA-9983 URL: https://issues.apache.org/jira/browse/KAFKA-9983 Project: Kafka Issue

[jira] [Commented] (KAFKA-9968) Newly subscribed topic not present in metadata request

[ https://issues.apache.org/jira/browse/KAFKA-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105860#comment-17105860 ] Rens Groothuijsen commented on KAFKA-9968: -- [~cmanhin] I personally wouldn't consider this

[jira] [Commented] (KAFKA-9968) Newly subscribed topic not present in metadata request

[ https://issues.apache.org/jira/browse/KAFKA-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105857#comment-17105857 ] Man Hin commented on KAFKA-9968: Thanks for the suggestions! I tried the test cases with extra poll. This

[jira] [Commented] (KAFKA-3184) Add Checkpoint for In-memory State Store

[ https://issues.apache.org/jira/browse/KAFKA-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105816#comment-17105816 ] Guozhang Wang commented on KAFKA-3184: -- Hello [~nizhikov] for many state-light applications, it is

[jira] [Commented] (KAFKA-9968) Newly subscribed topic not present in metadata request

[ https://issues.apache.org/jira/browse/KAFKA-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105792#comment-17105792 ] Rens Groothuijsen commented on KAFKA-9968: -- [~cmanhin] Thanks for the test case! From what I can

[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=17105745#comment-17105745 ] Raman Gupta commented on KAFKA-8803: [~guozhang] No, you never mentioned that commit above AFAICS. >

[jira] [Commented] (KAFKA-8820) kafka-reassign-partitions.sh should support the KIP-455 API

[ https://issues.apache.org/jira/browse/KAFKA-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105741#comment-17105741 ] Colin McCabe commented on KAFKA-8820: - Implemented in https://github.com/apache/kafka/pull/8244/ >

[jira] [Resolved] (KAFKA-8820) kafka-reassign-partitions.sh should support the KIP-455 API

[ https://issues.apache.org/jira/browse/KAFKA-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-8820. - Fix Version/s: 2.5.0 Resolution: Fixed > kafka-reassign-partitions.sh should support the

[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=17105739#comment-17105739 ] Guozhang Wang commented on KAFKA-8803: -- [~rocketraman] Did cherry-pick this commit as well?

[jira] [Commented] (KAFKA-9118) LogDirFailureHandler shouldn't use Zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105730#comment-17105730 ] Colin McCabe commented on KAFKA-9118: - Update: [~mumrah] now has a KIP for this posted at

[jira] [Created] (KAFKA-9982) [kafka-connect] Source connector does not guarantee at least once delivery

Qinghui Xu created KAFKA-9982: - Summary: [kafka-connect] Source connector does not guarantee at least once delivery Key: KAFKA-9982 URL: https://issues.apache.org/jira/browse/KAFKA-9982 Project: Kafka

[jira] [Updated] (KAFKA-9980) Text encoding bug prevents correctly setting client quotas for default entities

[ https://issues.apache.org/jira/browse/KAFKA-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe updated KAFKA-9980: Summary: Text encoding bug prevents correctly setting client quotas for default entities (was:

[jira] [Commented] (KAFKA-9603) Number of open files keeps increasing in Streams application

[ https://issues.apache.org/jira/browse/KAFKA-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105703#comment-17105703 ] Bruno Cadonna commented on KAFKA-9603: -- I think I found the cause of this issue. With segmented

[jira] [Reopened] (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:all-tabpanel ] Raman Gupta reopened KAFKA-8803: > Stream will not start due to TimeoutException: Timeout expired after > 6milliseconds while

[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=17105691#comment-17105691 ] Raman Gupta commented on KAFKA-8803: [~guozhang] Just ran into this problem again, with 2.4.1 + patch

[jira] [Updated] (KAFKA-9669) Kafka 2.4.0 Chokes on Filebeat 5.6 Produced Data

[ https://issues.apache.org/jira/browse/KAFKA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9669: --- Fix Version/s: 2.5.1 2.4.2 > Kafka 2.4.0 Chokes on Filebeat 5.6 Produced

[jira] [Updated] (KAFKA-9669) Kafka 2.4.0 Chokes on Filebeat 5.6 Produced Data

[ https://issues.apache.org/jira/browse/KAFKA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9669: --- Affects Version/s: 2.5.0 2.4.1 > Kafka 2.4.0 Chokes on Filebeat 5.6

[jira] [Resolved] (KAFKA-9669) Kafka 2.4.0 Chokes on Filebeat 5.6 Produced Data

[ https://issues.apache.org/jira/browse/KAFKA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9669. Resolution: Fixed > Kafka 2.4.0 Chokes on Filebeat 5.6 Produced Data >

[jira] [Updated] (KAFKA-9958) Expose Kafka Metrics in Authorizer

[ https://issues.apache.org/jira/browse/KAFKA-9958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Huang updated KAFKA-9958: -- Summary: Expose Kafka Metrics in Authorizer (was: Expose Kafka Metrics in AuthorizerServerInfo) >

[jira] [Commented] (KAFKA-9617) Replica Fetcher can mark partition as failed when max.message.bytes is changed

[ https://issues.apache.org/jira/browse/KAFKA-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105630#comment-17105630 ] Chia-Ping Tsai commented on KAFKA-9617: --- [~guozhang] thanks! > Replica Fetcher can mark partition

[jira] [Commented] (KAFKA-9953) support multiple consumerGroupCoordinators in TransactionManager

[ https://issues.apache.org/jira/browse/KAFKA-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105613#comment-17105613 ] Guozhang Wang commented on KAFKA-9953: -- Thanks [~jwijgerd]. Just to clarify I'm not questioning the

[jira] [Comment Edited] (KAFKA-9963) High CPU during replication of replaced (empty) broker

[ https://issues.apache.org/jira/browse/KAFKA-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105612#comment-17105612 ] Evan Williams edited comment on KAFKA-9963 at 5/12/20, 5:09 PM:

[jira] [Commented] (KAFKA-9963) High CPU during replication of replaced (empty) broker

[ https://issues.apache.org/jira/browse/KAFKA-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105612#comment-17105612 ] Evan Williams commented on KAFKA-9963: -- [~ishworgurung] Essentially on a 4vcpu (EC2 R5) instance, we

[jira] [Commented] (KAFKA-9963) High CPU during replication of replaced (empty) broker

[ https://issues.apache.org/jira/browse/KAFKA-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105606#comment-17105606 ] Ishwor Gurung commented on KAFKA-9963: -- [~blodsbror] Just out of curiosity, what was the issue? >

[jira] [Commented] (KAFKA-9071) transactional.id.expiration.ms config value should be implemented as a Long

[ https://issues.apache.org/jira/browse/KAFKA-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105584#comment-17105584 ] Joost van de Wijgerd commented on KAFKA-9071: - Hi, what's the status on this? would be great

[jira] [Comment Edited] (KAFKA-9953) support multiple consumerGroupCoordinators in TransactionManager

[ https://issues.apache.org/jira/browse/KAFKA-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105573#comment-17105573 ] Joost van de Wijgerd edited comment on KAFKA-9953 at 5/12/20, 4:38 PM:

[jira] [Comment Edited] (KAFKA-9953) support multiple consumerGroupCoordinators in TransactionManager

[ https://issues.apache.org/jira/browse/KAFKA-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105573#comment-17105573 ] Joost van de Wijgerd edited comment on KAFKA-9953 at 5/12/20, 4:38 PM:

[jira] [Comment Edited] (KAFKA-9953) support multiple consumerGroupCoordinators in TransactionManager

[ https://issues.apache.org/jira/browse/KAFKA-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105573#comment-17105573 ] Joost van de Wijgerd edited comment on KAFKA-9953 at 5/12/20, 4:37 PM:

[jira] [Commented] (KAFKA-9953) support multiple consumerGroupCoordinators in TransactionManager

[ https://issues.apache.org/jira/browse/KAFKA-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105573#comment-17105573 ] Joost van de Wijgerd commented on KAFKA-9953: - [~guozhang] our scenario is the following: 

[jira] [Resolved] (KAFKA-9963) High CPU during replication of replaced (empty) broker

[ https://issues.apache.org/jira/browse/KAFKA-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Williams resolved KAFKA-9963. -- Resolution: Abandoned > High CPU during replication of replaced (empty) broker >

[jira] [Commented] (KAFKA-9966) Flaky Test EosBetaUpgradeIntegrationTest#shouldUpgradeFromEosAlphaToEosBeta

[ https://issues.apache.org/jira/browse/KAFKA-9966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105545#comment-17105545 ] Bill Bejeck commented on KAFKA-9966:

[jira] [Commented] (KAFKA-9966) Flaky Test EosBetaUpgradeIntegrationTest#shouldUpgradeFromEosAlphaToEosBeta

[ https://issues.apache.org/jira/browse/KAFKA-9966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105544#comment-17105544 ] Bill Bejeck commented on KAFKA-9966:

[jira] [Created] (KAFKA-9981) Running a dedicated mm2 cluster with more than one nodes,When the configuration is updated the task is not aware and will lose the update operation.

victor created KAFKA-9981: - Summary: Running a dedicated mm2 cluster with more than one nodes,When the configuration is updated the task is not aware and will lose the update operation. Key: KAFKA-9981 URL:

[jira] [Commented] (KAFKA-9931) Kafka Connect should accept '-1' as a valid replication factor

[ https://issues.apache.org/jira/browse/KAFKA-9931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105484#comment-17105484 ] Randall Hauch commented on KAFKA-9931: -- While working on the aforementioned PR, I stumbled upon some

[jira] [Comment Edited] (KAFKA-9931) Kafka Connect should accept '-1' as a valid replication factor

[ https://issues.apache.org/jira/browse/KAFKA-9931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105473#comment-17105473 ] Randall Hauch edited comment on KAFKA-9931 at 5/12/20, 2:20 PM: Created

[jira] [Comment Edited] (KAFKA-9931) Kafka Connect should accept '-1' as a valid replication factor

[ https://issues.apache.org/jira/browse/KAFKA-9931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105473#comment-17105473 ] Randall Hauch edited comment on KAFKA-9931 at 5/12/20, 2:20 PM: Created

[jira] [Commented] (KAFKA-9951) More testing of ReplicaSelector

[ https://issues.apache.org/jira/browse/KAFKA-9951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105404#comment-17105404 ] Tom Bentley commented on KAFKA-9951: [~hachikuji] the {{RackAwareSelector}} has

[jira] [Assigned] (KAFKA-9603) Number of open files keeps increasing in Streams application

[ https://issues.apache.org/jira/browse/KAFKA-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-9603: Assignee: Bruno Cadonna > Number of open files keeps increasing in Streams application >

[jira] [Resolved] (KAFKA-5948) EosIntegrationTest fails with TopicAlreadyMarkedForDeletionException

[ https://issues.apache.org/jira/browse/KAFKA-5948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-5948. -- Resolution: Cannot Reproduce > EosIntegrationTest fails with

[jira] [Commented] (KAFKA-7224) KIP-328: Add spill-to-disk for Suppression

[ https://issues.apache.org/jira/browse/KAFKA-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105278#comment-17105278 ] Maatari commented on KAFKA-7224: Got it. Many thanks. > KIP-328: Add spill-to-disk for Suppression >

[jira] [Updated] (KAFKA-9980) Reserved word "" may not be santinized to "%3Cdefault%3E"

[ https://issues.apache.org/jira/browse/KAFKA-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Tan updated KAFKA-9980: - Description: quota_tests.py is failing. Specifically for this test: {quote} [INFO:2020-05-11

[jira] [Commented] (KAFKA-9980) Reserved word "" may not be santinized to "%3Cdefault%3E"

[ https://issues.apache.org/jira/browse/KAFKA-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105194#comment-17105194 ] Cheng Tan commented on KAFKA-9980: -- Patch here: [https://github.com/apache/kafka/pull/8652/files] >

[jira] [Assigned] (KAFKA-9980) Reserved word "" may not be santinized to "%3Cdefault%3E"

[ https://issues.apache.org/jira/browse/KAFKA-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Tan reassigned KAFKA-9980: Assignee: Cheng Tan > Reserved word "" may not be santinized to "%3Cdefault%3E" >

[jira] [Created] (KAFKA-9980) Reserved word "" may not be santinized to "%3Cdefault%3E"

Cheng Tan created KAFKA-9980: Summary: Reserved word "" may not be santinized to "%3Cdefault%3E" Key: KAFKA-9980 URL: https://issues.apache.org/jira/browse/KAFKA-9980 Project: Kafka Issue Type: