[jira] [Commented] (KAFKA-6029) Controller should wait for the leader migration to finish before ack a ControlledShutdownRequest

[ https://issues.apache.org/jira/browse/KAFKA-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840876#comment-16840876 ] Colin P. McCabe commented on KAFKA-6029: This sounds like a good improvement. I can take the

[jira] [Created] (KAFKA-8374) KafkaApis.handleLeaderAndIsrRequest not robust to ZooKeeper exceptions

Mike Mintz created KAFKA-8374: - Summary: KafkaApis.handleLeaderAndIsrRequest not robust to ZooKeeper exceptions Key: KAFKA-8374 URL: https://issues.apache.org/jira/browse/KAFKA-8374 Project: Kafka

[jira] [Created] (KAFKA-8373) Add group.instance.id field into Sync/Heartbeat/OffsetCommit protocols

Boyang Chen created KAFKA-8373: -- Summary: Add group.instance.id field into Sync/Heartbeat/OffsetCommit protocols Key: KAFKA-8373 URL: https://issues.apache.org/jira/browse/KAFKA-8373 Project: Kafka

[jira] [Commented] (KAFKA-8215) Limit memory usage of RocksDB

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

[jira] [Commented] (KAFKA-8347) Choose next record to process by timestamp

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

[jira] [Commented] (KAFKA-8347) Choose next record to process by timestamp

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

[jira] [Commented] (KAFKA-8320) Connect Error handling is using the RetriableException from common package

[ https://issues.apache.org/jira/browse/KAFKA-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840826#comment-16840826 ] ASF GitHub Bot commented on KAFKA-8320: --- rhauch commented on pull request #6675: KAFKA-8320 : fix

[jira] [Created] (KAFKA-8372) Remove deprecated RocksDB#compactRange API

Sophie Blee-Goldman created KAFKA-8372: -- Summary: Remove deprecated RocksDB#compactRange API Key: KAFKA-8372 URL: https://issues.apache.org/jira/browse/KAFKA-8372 Project: Kafka Issue

[jira] [Commented] (KAFKA-8354) Replace SyncGroup request/response with automated protocol

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

[jira] [Resolved] (KAFKA-5061) client.id should be set for Connect producers/consumers

[ https://issues.apache.org/jira/browse/KAFKA-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5061. -- Resolution: Fixed > client.id should be set for Connect producers/consumers >

[jira] [Updated] (KAFKA-5061) client.id should be set for Connect producers/consumers

[ https://issues.apache.org/jira/browse/KAFKA-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5061: - Reviewer: Randall Hauch Fix Version/s: 2.3.0 > client.id should be set for Connect

[jira] [Commented] (KAFKA-5061) client.id should be set for Connect producers/consumers

[ https://issues.apache.org/jira/browse/KAFKA-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840813#comment-16840813 ] ASF GitHub Bot commented on KAFKA-5061: --- rhauch commented on pull request #6097: KAFKA-5061 - Make

[jira] [Commented] (KAFKA-8215) Limit memory usage of RocksDB

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

[jira] [Updated] (KAFKA-8195) Unstable Producer After Send Failure in Transaction

[ https://issues.apache.org/jira/browse/KAFKA-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-8195: --- Priority: Major (was: Blocker) > Unstable Producer After Send Failure in

[jira] [Commented] (KAFKA-7504) Broker performance degradation caused by call of sendfile reading disk in network thread

[ https://issues.apache.org/jira/browse/KAFKA-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840732#comment-16840732 ] Allen Wang commented on KAFKA-7504: --- [~junrao] [~ijuma] Any plan to address this performance issue in

[jira] [Created] (KAFKA-8371) Remove ReplicaManager dependence from Partition

Jason Gustafson created KAFKA-8371: -- Summary: Remove ReplicaManager dependence from Partition Key: KAFKA-8371 URL: https://issues.apache.org/jira/browse/KAFKA-8371 Project: Kafka Issue

[jira] [Created] (KAFKA-8370) Kafka Connect should check for existence of internal topics before attempting to create them

Randall Hauch created KAFKA-8370: Summary: Kafka Connect should check for existence of internal topics before attempting to create them Key: KAFKA-8370 URL: https://issues.apache.org/jira/browse/KAFKA-8370

[jira] [Commented] (KAFKA-7670) Fix flaky test - KafkaAdminClientTest.testUnreachableBootstrapServer

[ https://issues.apache.org/jira/browse/KAFKA-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840676#comment-16840676 ] Boyang Chen commented on KAFKA-7670: Hey Stanis, seems that test gets flakey again: 

[jira] [Created] (KAFKA-8369) Generate an immutable Map view for generated messages with a map key

Jason Gustafson created KAFKA-8369: -- Summary: Generate an immutable Map view for generated messages with a map key Key: KAFKA-8369 URL: https://issues.apache.org/jira/browse/KAFKA-8369 Project:

[jira] [Commented] (KAFKA-8367) Non-heap memory leak in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840590#comment-16840590 ] Sophie Blee-Goldman commented on KAFKA-8367: Sorry, commented before I read the ticket. As

[jira] [Issue Comment Deleted] (KAFKA-8367) Non-heap memory leak in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sophie Blee-Goldman updated KAFKA-8367: --- Comment: was deleted (was: Actually, even if you are not using the ConfigSetter the

[jira] [Commented] (KAFKA-8367) Non-heap memory leak in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840588#comment-16840588 ] Sophie Blee-Goldman commented on KAFKA-8367: Actually, even if you are not using the

[jira] [Commented] (KAFKA-8195) Unstable Producer After Send Failure in Transaction

[ https://issues.apache.org/jira/browse/KAFKA-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840587#comment-16840587 ] Gary Russell commented on KAFKA-8195: - I can confirm that, when using a size limit of 1000 (and

[jira] [Commented] (KAFKA-8195) Unstable Producer After Send Failure in Transaction

[ https://issues.apache.org/jira/browse/KAFKA-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840572#comment-16840572 ] Gary Russell commented on KAFKA-8195: - I understand, but since I'm not really the originator of the

[jira] [Comment Edited] (KAFKA-8195) Unstable Producer After Send Failure in Transaction

[ https://issues.apache.org/jira/browse/KAFKA-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840543#comment-16840543 ] Viktor Somogyi-Vass edited comment on KAFKA-8195 at 5/15/19 4:25 PM: -

[jira] [Commented] (KAFKA-8195) Unstable Producer After Send Failure in Transaction

[ https://issues.apache.org/jira/browse/KAFKA-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840543#comment-16840543 ] Viktor Somogyi-Vass commented on KAFKA-8195: [~grussell] I think I got the full picture on

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840541#comment-16840541 ] Andrew commented on KAFKA-8315: --- [~vvcephei] [~ableegoldman] I have constructed an integration test that I

[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=16840537#comment-16840537 ] John Roesler commented on KAFKA-6474: - Hey, [~h314to], I just sent

[jira] [Commented] (KAFKA-8367) Non-heap memory leak in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840533#comment-16840533 ] John Roesler commented on KAFKA-8367: - Hi [~pavelsavov], It looks like you might be using a RockDB

[jira] [Created] (KAFKA-8368) Errors when attempting to use connectors that are in multiple Kafka Connect plugins

Randall Hauch created KAFKA-8368: Summary: Errors when attempting to use connectors that are in multiple Kafka Connect plugins Key: KAFKA-8368 URL: https://issues.apache.org/jira/browse/KAFKA-8368

[jira] [Updated] (KAFKA-8367) Non-heap memory leak in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Savov updated KAFKA-8367: --- Description: We have been observing a non-heap memory leak after upgrading to Kafka Streams 2.2.0

[jira] [Updated] (KAFKA-8367) Non-heap memory leak in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Savov updated KAFKA-8367: --- Description: We have been observing a non-heap memory leak after upgrading to Kafka Streams 2.2.0

[jira] [Created] (KAFKA-8367) Non-heap memory leak in Kafka Streams

Pavel Savov created KAFKA-8367: -- Summary: Non-heap memory leak in Kafka Streams Key: KAFKA-8367 URL: https://issues.apache.org/jira/browse/KAFKA-8367 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-8359) Reconsider default for leader imbalance percentage

[ https://issues.apache.org/jira/browse/KAFKA-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840262#comment-16840262 ] Sönke Liebau commented on KAFKA-8359: - I dug around a little as to where this default comes from, but

[jira] [Commented] (KAFKA-8336) Enable dynamic update of client-side SSL factory in brokers

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

[jira] [Resolved] (KAFKA-8336) Enable dynamic update of client-side SSL factory in brokers

[ https://issues.apache.org/jira/browse/KAFKA-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-8336. --- Resolution: Fixed Reviewer: Manikumar > Enable dynamic update of client-side SSL