[jira] [Commented] (KAFKA-6676) System tests do not handle ZK chroot properly with SCRAM

[ https://issues.apache.org/jira/browse/KAFKA-6676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403741#comment-16403741 ] ASF GitHub Bot commented on KAFKA-6676: --- ewencp opened a new pull request #4729: KAFKA-6676: Ensure

[jira] [Created] (KAFKA-6676) System tests do not handle ZK chroot properly with SCRAM

Ewen Cheslack-Postava created KAFKA-6676: Summary: System tests do not handle ZK chroot properly with SCRAM Key: KAFKA-6676 URL: https://issues.apache.org/jira/browse/KAFKA-6676 Project: Kafka

[jira] [Created] (KAFKA-6675) Connect workers should log plugin path and available plugins more clearly

Randall Hauch created KAFKA-6675: Summary: Connect workers should log plugin path and available plugins more clearly Key: KAFKA-6675 URL: https://issues.apache.org/jira/browse/KAFKA-6675 Project:

[jira] [Updated] (KAFKA-6208) Reduce startup time for Kafka Connect workers

[ https://issues.apache.org/jira/browse/KAFKA-6208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6208: - Labels: needs-kip (was: ) > Reduce startup time for Kafka Connect workers >

[jira] [Resolved] (KAFKA-6674) Kafka start script does not work on ibm jre

[ https://issues.apache.org/jira/browse/KAFKA-6674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamar Thais resolved KAFKA-6674. Resolution: Duplicate Fix Version/s: (was: 1.0.2) Duplicate with

[jira] [Created] (KAFKA-6674) Kafka start script does not work on ibm jre

Tamar Thais created KAFKA-6674: -- Summary: Kafka start script does not work on ibm jre Key: KAFKA-6674 URL: https://issues.apache.org/jira/browse/KAFKA-6674 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-6530) Use actual first offset of messages when rolling log segment for magic v2

[ https://issues.apache.org/jira/browse/KAFKA-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403560#comment-16403560 ] Dhruvil Shah commented on KAFKA-6530: - Thanks! On Sat, Mar 17, 2018 at 10:31 AM Jason Gustafson

[jira] [Resolved] (KAFKA-6530) Use actual first offset of messages when rolling log segment for magic v2

[ https://issues.apache.org/jira/browse/KAFKA-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6530. Resolution: Fixed Fix Version/s: 1.2.0 > Use actual first offset of messages when

[jira] [Commented] (KAFKA-6530) Use actual first offset of messages when rolling log segment for magic v2

[ https://issues.apache.org/jira/browse/KAFKA-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403558#comment-16403558 ] ASF GitHub Bot commented on KAFKA-6530: --- hachikuji closed pull request #4660: KAFKA-6530: Use actual

[jira] [Resolved] (KAFKA-6338) java.lang.NoClassDefFoundError: org/apache/kafka/common/network/LoginType

[ https://issues.apache.org/jira/browse/KAFKA-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6338. -- Resolution: Not A Problem Closing this  in-favor of RANGER-1964 > java.lang.NoClassDefFoundError:

[jira] [Resolved] (KAFKA-6596) Why we can not see any consumer offset produce rate in kafka manager

[ https://issues.apache.org/jira/browse/KAFKA-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6596. -- Resolution: Not A Problem I suggest you to reach out kafka-manager mailing list/github community for

[jira] [Commented] (KAFKA-6613) The controller shouldn't stop partition reassignment after an exception is being thrown

[ https://issues.apache.org/jira/browse/KAFKA-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403454#comment-16403454 ] Manikumar commented on KAFKA-6613: -- This might have fixed in KAFKA-5758 > The controller shouldn't stop

[jira] [Resolved] (KAFKA-5187) producer.close() times out at 30 seconds

[ https://issues.apache.org/jira/browse/KAFKA-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5187. -- Resolution: Not A Problem Please reopen if the issue still exists. > producer.close() times out at 30

[jira] [Resolved] (KAFKA-4782) change chroot for a kafka instance

[ https://issues.apache.org/jira/browse/KAFKA-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4782. -- Resolution: Not A Problem > change chroot for a kafka instance > -- > >

[jira] [Resolved] (KAFKA-3553) Issue with getting data of next offset after restarting the consumer and producer is always running

[ https://issues.apache.org/jira/browse/KAFKA-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3553. -- Resolution: Auto Closed {color:#00}Closing inactive issue. Please raise issue with kafka-python

[jira] [Resolved] (KAFKA-3550) Broker does not honor MetadataRequest api version; always returns v0 MetadataResponse

[ https://issues.apache.org/jira/browse/KAFKA-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3550. -- Resolution: Fixed Closing as per above comment. > Broker does not honor MetadataRequest api version;

[jira] [Resolved] (KAFKA-3238) Deadlock Mirrormaker consumer not fetching any messages

[ https://issues.apache.org/jira/browse/KAFKA-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3238. -- Resolution: Auto Closed Closing inactive issue.  old consumer client is no longer supported.  In newer

[jira] [Resolved] (KAFKA-1106) HighwaterMarkCheckpoint failure puting broker into a bad state

[ https://issues.apache.org/jira/browse/KAFKA-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1106. -- Resolution: Auto Closed Relevant parts of the code is changed an similar exceptions are fixed in the