[jira] [Resolved] (KAFKA-6680) Fix config initialization in DynamicBrokerConfig

[ https://issues.apache.org/jira/browse/KAFKA-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6680. -- Resolution: Fixed Fix Version/s: (was: 1.2.0) 1.1.0 > Fix config initializ

[jira] [Comment Edited] (KAFKA-6682) Kafka reconnection after broker restart

[ https://issues.apache.org/jira/browse/KAFKA-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406717#comment-16406717 ] Manikumar edited comment on KAFKA-6682 at 3/20/18 5:14 PM: --- Look

[jira] [Commented] (KAFKA-6682) Kafka reconnection after broker restart

[ https://issues.apache.org/jira/browse/KAFKA-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406717#comment-16406717 ] Manikumar commented on KAFKA-6682: -- Looks like this fixed in : https://issues.apache.org/

[jira] [Comment Edited] (KAFKA-6689) Kafka not release .deleted file.

[ https://issues.apache.org/jira/browse/KAFKA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16405870#comment-16405870 ] Manikumar edited comment on KAFKA-6689 at 3/20/18 7:05 AM: --- Thes

[jira] [Commented] (KAFKA-6689) Kafka not release .deleted file.

[ https://issues.apache.org/jira/browse/KAFKA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16405870#comment-16405870 ] Manikumar commented on KAFKA-6689: -- There temp files will be deleted after file.delete.de

[jira] [Assigned] (KAFKA-6680) Fix config initialization in DynamicBrokerConfig

[ https://issues.apache.org/jira/browse/KAFKA-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-6680: Assignee: Manikumar Fix Version/s: 1.2.0 PR: https://github.com/apache/kafka/pull/4731 >

[jira] [Created] (KAFKA-6680) Fix config initialization in DynamicBrokerConfig

Manikumar created KAFKA-6680: Summary: Fix config initialization in DynamicBrokerConfig Key: KAFKA-6680 URL: https://issues.apache.org/jira/browse/KAFKA-6680 Project: Kafka Issue Type: Bug

[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: org/a

[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 any

[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&focusedCommentId=16403454#comment-16403454 ] Manikumar commented on KAFKA-6613: -- This might have fixed in KAFKA-5758 > The controller

[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 s

[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 pro

[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; al

[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 ne

[jira] [Resolved] (KAFKA-4027) Leader for a cetain partition unavailable forever

[ https://issues.apache.org/jira/browse/KAFKA-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4027. -- Resolution: Duplicate This behavior is changed in KAFKA-5758.  Please reopen if you think the issue sti

[jira] [Commented] (KAFKA-4027) Leader for a cetain partition unavailable forever

[ https://issues.apache.org/jira/browse/KAFKA-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397208#comment-16397208 ] Manikumar commented on KAFKA-4027: -- More details about similar exception are here: https

[jira] [Resolved] (KAFKA-4984) Unable to produce or consume when enabling authentication SASL/Kerberos

[ https://issues.apache.org/jira/browse/KAFKA-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4984. -- Resolution: Cannot Reproduce {color:#00}Closing inactive issue. Please reopen if you think the issue

[jira] [Resolved] (KAFKA-5504) Kafka controller is not getting elected

[ https://issues.apache.org/jira/browse/KAFKA-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5504. -- Resolution: Not A Problem Closing as per above comments. > Kafka controller is not getting elected > --

[jira] [Resolved] (KAFKA-6022) mirror maker stores offset in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6022. -- Resolution: Not A Problem Please reopen if you think the issue still exists > mirror maker stores offse

[jira] [Resolved] (KAFKA-5467) setting offset retention minutes to a lower value is not reflecting

[ https://issues.apache.org/jira/browse/KAFKA-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5467. -- Resolution: Cannot Reproduce Closing inactive issue. Please reopen if you think the issue exists. > set

[jira] [Resolved] (KAFKA-6337) Error for partition [__consumer_offsets,15] to broker

[ https://issues.apache.org/jira/browse/KAFKA-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6337. -- Resolution: Cannot Reproduce Please reopen if you think the issue still exists > Error for partition [_

[jira] [Comment Edited] (KAFKA-6584) Session expiration concurrent with ZooKeeper leadership failover may lead to broker registration failure

[ https://issues.apache.org/jira/browse/KAFKA-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376591#comment-16376591 ] Manikumar edited comment on KAFKA-6584 at 2/26/18 9:39 AM: --- Than

[jira] [Commented] (KAFKA-6584) Session expiration concurrent with ZooKeeper leadership failover may lead to broker registration failure

[ https://issues.apache.org/jira/browse/KAFKA-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376591#comment-16376591 ] Manikumar commented on KAFKA-6584: -- Thanks for details.  looks like this is the root caus

[jira] [Resolved] (KAFKA-5809) when zookeeper set acl on path /. then kafka can't connect zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5809. -- Resolution: Won't Fix either we need to remove the acls on zk node acls or enable Zk SASL authenticatio

[jira] [Resolved] (KAFKA-2553) Kafka Consumer Hangs after Network Partition

[ https://issues.apache.org/jira/browse/KAFKA-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2553. -- Resolution: Fixed Similar issues are in KAFKA-2169. Pl reopen if the issue still exists > Kafka Consume

[jira] [Resolved] (KAFKA-2796) add support for reassignment partition to specified logdir

[ https://issues.apache.org/jira/browse/KAFKA-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2796. -- Resolution: Fixed Fixed in KIP-113 (KAFKA-5163/KAFKA-5694) > add support for reassignment partition to

[jira] [Resolved] (KAFKA-902) Randomize backoff on the clients for metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-902. - Resolution: Fixed Resolving this Duplicate of KAFKA-3878. Pls reopen if you think otherwise. > Randomize b

[jira] [Resolved] (KAFKA-2167) ZkUtils updateEphemeralPath JavaDoc (spelling and correctness)

[ https://issues.apache.org/jira/browse/KAFKA-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2167. -- Resolution: Fixed > ZkUtils updateEphemeralPath JavaDoc (spelling and correctness) > ---

[jira] [Commented] (KAFKA-6564) Fix broken links in Dockerfile

[ https://issues.apache.org/jira/browse/KAFKA-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365510#comment-16365510 ] Manikumar commented on KAFKA-6564: -- This was fixed in -KAFKA-6247-  > Fix broken links i

[jira] [Commented] (KAFKA-6549) Deadlock while processing Controller Events

[ https://issues.apache.org/jira/browse/KAFKA-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360879#comment-16360879 ] Manikumar commented on KAFKA-6549: -- Below are the sequence of steps which led to deadlock

[jira] [Commented] (KAFKA-6549) Deadlock while processing Controller Events

[ https://issues.apache.org/jira/browse/KAFKA-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358859#comment-16358859 ] Manikumar commented on KAFKA-6549: -- This is not exactly deadlock. ZooKeeperClient request

[jira] [Updated] (KAFKA-6549) Deadlock while processing Controller Events

[ https://issues.apache.org/jira/browse/KAFKA-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-6549: - Summary: Deadlock while processing Controller Events (was: Deadlock in ZookeeperClient while processing C

[jira] [Created] (KAFKA-6549) Deadlock in ZookeeperClient while processing Controller Events

Manikumar created KAFKA-6549: Summary: Deadlock in ZookeeperClient while processing Controller Events Key: KAFKA-6549 URL: https://issues.apache.org/jira/browse/KAFKA-6549 Project: Kafka Issue T

[jira] [Commented] (KAFKA-6524) kafka mirror can't producer internal topic

[ https://issues.apache.org/jira/browse/KAFKA-6524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16355377#comment-16355377 ] Manikumar commented on KAFKA-6524: -- [~huxi_2b] Thanks for the pointer. looked into the c

[jira] [Commented] (KAFKA-6524) kafka mirror can't producer internal topic

[ https://issues.apache.org/jira/browse/KAFKA-6524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16355320#comment-16355320 ] Manikumar commented on KAFKA-6524: -- [~huxi_2b] Not sure how "client.id" affects producing

[jira] [Commented] (KAFKA-6524) kafka mirror can't producer internal topic

[ https://issues.apache.org/jira/browse/KAFKA-6524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350186#comment-16350186 ] Manikumar commented on KAFKA-6524: -- exclude.internal.topics only for consumer clients. We

[jira] [Commented] (KAFKA-6496) NAT and Kafka

[ https://issues.apache.org/jira/browse/KAFKA-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349884#comment-16349884 ] Manikumar commented on KAFKA-6496: -- Try configuring "advertised.listeners" config propert

[jira] [Commented] (KAFKA-2404) Delete config znode when config values are empty

[ https://issues.apache.org/jira/browse/KAFKA-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347310#comment-16347310 ] Manikumar commented on KAFKA-2404: -- looks like this is tricky to implement. We can only r

[jira] [Assigned] (KAFKA-6452) Add documentation for delegation token authentication mechanism

[ https://issues.apache.org/jira/browse/KAFKA-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-6452: Assignee: Manikumar Fix Version/s: 1.1.0 Component/s: documentation > Add documentat

[jira] [Resolved] (KAFKA-6091) Authorization API is called hundred's of times when there are no privileges

[ https://issues.apache.org/jira/browse/KAFKA-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6091. -- Resolution: Fixed Fixed via KAFKA-5547. Please reopen if you think the issue still exists > Authorizati

[jira] [Resolved] (KAFKA-4185) Abstract out password verifier in SaslServer as an injectable dependency

[ https://issues.apache.org/jira/browse/KAFKA-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4185. -- Resolution: Duplicate Closing this in favor of KIP-86/KAFKA-4292. Please reopen if you think otherwise

[jira] [Resolved] (KAFKA-3408) consumer rebalance fail

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

[jira] [Resolved] (KAFKA-5617) Update to the list of third-party clients

[ https://issues.apache.org/jira/browse/KAFKA-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5617. -- Resolution: Fixed > Update to the list of third-party clients >

[jira] [Resolved] (KAFKA-5500) it is impossible to have custom Login Modules for PLAIN SASL mechanism

[ https://issues.apache.org/jira/browse/KAFKA-5500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5500. -- Resolution: Duplicate Closing in favor of KIP-88/KAFKA-4292.  Please reopen if you think otherwise. > i

[jira] [Resolved] (KAFKA-1458) kafka hanging on shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1458. -- Resolution: Auto Closed {color:#00}Closing inactive issue. Please reopen if you think the issue sti

[jira] [Resolved] (KAFKA-1475) Kafka consumer stops LeaderFinder/FetcherThreads, but application does not know

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

[jira] [Resolved] (KAFKA-4256) Use IP for ZK broker register

[ https://issues.apache.org/jira/browse/KAFKA-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4256. -- Resolution: Won't Fix Closing as per above comment. Pls reopen If the issue still exists. > Use IP for

[jira] [Created] (KAFKA-6452) Add documentation for delegation token authentication mechanism

Manikumar created KAFKA-6452: Summary: Add documentation for delegation token authentication mechanism Key: KAFKA-6452 URL: https://issues.apache.org/jira/browse/KAFKA-6452 Project: Kafka Issue

[jira] [Updated] (KAFKA-4542) Add authentication based on delegation token.

[ https://issues.apache.org/jira/browse/KAFKA-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-4542: - Fix Version/s: 1.1.0 > Add authentication based on delegation token. > ---

[jira] [Resolved] (KAFKA-4542) Add authentication based on delegation token.

[ https://issues.apache.org/jira/browse/KAFKA-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4542. -- Resolution: Fixed Fixed via [https://github.com/apache/kafka/pull/3616] > Add authentication based on d

[jira] [Resolved] (KAFKA-4543) Add capability to renew/expire delegation tokens.

[ https://issues.apache.org/jira/browse/KAFKA-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4543. -- Resolution: Fixed Fix Version/s: 1.1.0 Fixed via [https://github.com/apache/kafka/pull/3616] > A

[jira] [Updated] (KAFKA-6447) Add Delegation Token Operations to KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-6447: - Description: This JIRA is about adding delegation token operations to the new Admin Client API. KIP: ht

[jira] [Created] (KAFKA-6447) Add Delegation Token Operations to KafkaAdminClient

Manikumar created KAFKA-6447: Summary: Add Delegation Token Operations to KafkaAdminClient Key: KAFKA-6447 URL: https://issues.apache.org/jira/browse/KAFKA-6447 Project: Kafka Issue Type: Sub-tas

[jira] [Resolved] (KAFKA-2331) Kafka does not spread partitions in a topic among all consumers evenly

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

[jira] [Resolved] (KAFKA-2329) Consumers balance fails when multiple consumers are started simultaneously.

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

[jira] [Resolved] (KAFKA-2025) In multi-consumer setup - explicit commit, commits on all partitions

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

[jira] [Resolved] (KAFKA-1229) Reload broker config without a restart

[ https://issues.apache.org/jira/browse/KAFKA-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1229. -- Resolution: Duplicate Resolving as duplicate of KIP-226/KAFKA-6240. Pls reopen of any concern. > Reload

[jira] [Assigned] (KAFKA-5624) Unsafe use of expired sensors

[ https://issues.apache.org/jira/browse/KAFKA-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-5624: Assignee: Manikumar > Unsafe use of expired sensors > - > >

[jira] [Resolved] (KAFKA-6171) [1.0.0] Logging is broken with Windows and Java 9

[ https://issues.apache.org/jira/browse/KAFKA-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6171. -- Resolution: Duplicate > [1.0.0] Logging is broken with Windows and Java 9 >

[jira] [Resolved] (KAFKA-5850) Py4JJavaError: An error occurred while calling o40.loadClass. : java.lang.ClassNotFoundException: org.apache.spark.streaming.kafka.KafkaUtilsPythonHelper

[ https://issues.apache.org/jira/browse/KAFKA-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5850. -- Resolution: Invalid Please reopen if you think the issue is related to kafka > Py4JJavaError: An err

[jira] [Commented] (KAFKA-6312) Add documentation about kafka-consumer-groups.sh's ability to set/change offsets

[ https://issues.apache.org/jira/browse/KAFKA-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318089#comment-16318089 ] Manikumar commented on KAFKA-6312: -- [~prasanna1433] You can follow below links: http://k

[jira] [Resolved] (KAFKA-3893) Kafka Broker ID disappears from /brokers/ids

[ https://issues.apache.org/jira/browse/KAFKA-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3893. -- Resolution: Fixed Please reopen if the issue still exists. > Kafka Broker ID disappears from /broker

[jira] [Resolved] (KAFKA-6077) Let SimpleConsumer support Kerberos authentication

[ https://issues.apache.org/jira/browse/KAFKA-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6077. -- Resolution: Won't Fix The old consumer is no longer supported, please consider above mentioned options.

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16313010#comment-16313010 ] Manikumar commented on KAFKA-6338: -- Some of the code/api got changed in Kafka 0.11. This

[jira] [Commented] (KAFKA-6426) Kafka SASL/SCRAM authentication does not fail for incorrect username or password.

[ https://issues.apache.org/jira/browse/KAFKA-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312902#comment-16312902 ] Manikumar commented on KAFKA-6426: -- looks like still you are having config issues. you ne

[jira] [Commented] (KAFKA-6426) Kafka SASL/SCRAM authentication does not fail for incorrect username or password.

[ https://issues.apache.org/jira/browse/KAFKA-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312807#comment-16312807 ] Manikumar commented on KAFKA-6426: -- In producer.properties file, security.protocol is se

[jira] [Assigned] (KAFKA-4897) LogCleaner#cleanSegments should not ignore failures to delete files

[ https://issues.apache.org/jira/browse/KAFKA-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-4897: Assignee: Manikumar > LogCleaner#cleanSegments should not ignore failures to delete files > ---

[jira] [Commented] (KAFKA-4897) LogCleaner#cleanSegments should not ignore failures to delete files

[ https://issues.apache.org/jira/browse/KAFKA-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312588#comment-16312588 ] Manikumar commented on KAFKA-4897: -- looks like this got handled in KAFKA-6324 cc [~ijuma

[jira] [Resolved] (KAFKA-6380) transient failure in MetricsTest.testMetrics

[ https://issues.apache.org/jira/browse/KAFKA-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6380. -- Resolution: Won't Fix Related code is getting changed in KAFKA-6320. > transient failure in MetricsTe

[jira] [Commented] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297972#comment-16297972 ] Manikumar commented on KAFKA-5407: -- [~hachikuji] Your thoughts on propagating offsets top

[jira] [Created] (KAFKA-6380) transient failure in MetricsTest.testMetrics

Manikumar created KAFKA-6380: Summary: transient failure in MetricsTest.testMetrics Key: KAFKA-6380 URL: https://issues.apache.org/jira/browse/KAFKA-6380 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-6335) SimpleAclAuthorizerTest#testHighConcurrencyModificationOfResourceAcls fails intermittently

[ https://issues.apache.org/jira/browse/KAFKA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289773#comment-16289773 ] Manikumar commented on KAFKA-6335: -- SimpleAclAuthorizer#updateResourceAcls() will retry i

[jira] [Assigned] (KAFKA-6335) SimpleAclAuthorizerTest#testHighConcurrencyModificationOfResourceAcls fails intermittently

[ https://issues.apache.org/jira/browse/KAFKA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-6335: Assignee: Manikumar > SimpleAclAuthorizerTest#testHighConcurrencyModificationOfResourceAcls fails

[jira] [Commented] (KAFKA-6343) OOM as the result of creation of 5k topics

[ https://issues.apache.org/jira/browse/KAFKA-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285841#comment-16285841 ] Manikumar commented on KAFKA-6343: -- Can you post the output of "ulimit -a" and "ps -ef

[jira] [Commented] (KAFKA-6337) Error for partition [__consumer_offsets,15] to broker

[ https://issues.apache.org/jira/browse/KAFKA-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285808#comment-16285808 ] Manikumar commented on KAFKA-6337: -- Yes, 30 Seconds should be fine for most of the envir

[jira] [Commented] (KAFKA-6337) Error for partition [__consumer_offsets,15] to broker

[ https://issues.apache.org/jira/browse/KAFKA-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285730#comment-16285730 ] Manikumar commented on KAFKA-6337: -- This is due to zk session expiration. This should be

[jira] [Commented] (KAFKA-6199) Single broker with fast growing heap usage

[ https://issues.apache.org/jira/browse/KAFKA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282116#comment-16282116 ] Manikumar commented on KAFKA-6199: -- [~rt_skyscanner] yes, jstack output > Single broker

[jira] [Commented] (KAFKA-6199) Single broker with fast growing heap usage

[ https://issues.apache.org/jira/browse/KAFKA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282041#comment-16282041 ] Manikumar commented on KAFKA-6199: -- Are there any exceptions in the broker? Can you uplo

[jira] [Commented] (KAFKA-6199) Single broker with fast growing heap usage

[ https://issues.apache.org/jira/browse/KAFKA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276917#comment-16276917 ] Manikumar commented on KAFKA-6199: -- histogram shows large number (~7000) of KafkaChannel/

[jira] [Commented] (KAFKA-6281) Kafka JavaAPI Producer failed with NotLeaderForPartitionException

[ https://issues.apache.org/jira/browse/KAFKA-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272566#comment-16272566 ] Manikumar commented on KAFKA-6281: -- [~anilkumar...@gmail.com] As mentioned in previous co

[jira] [Commented] (KAFKA-6281) Kafka JavaAPI Producer failed with NotLeaderForPartitionException

[ https://issues.apache.org/jira/browse/KAFKA-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270767#comment-16270767 ] Manikumar commented on KAFKA-6281: -- [~anilkumar...@gmail.com] 2mins is high value. increa

[jira] [Comment Edited] (KAFKA-6281) Kafka JavaAPI Producer failed with NotLeaderForPartitionException

[ https://issues.apache.org/jira/browse/KAFKA-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270588#comment-16270588 ] Manikumar edited comment on KAFKA-6281 at 11/29/17 10:56 AM: -

[jira] [Commented] (KAFKA-6281) Kafka JavaAPI Producer failed with NotLeaderForPartitionException

[ https://issues.apache.org/jira/browse/KAFKA-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270588#comment-16270588 ] Manikumar commented on KAFKA-6281: -- looks ZK session expired on the broker. Whenever thi

[jira] [Commented] (KAFKA-6199) Single broker with fast growing heap usage

[ https://issues.apache.org/jira/browse/KAFKA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267029#comment-16267029 ] Manikumar commented on KAFKA-6199: -- [~rt_skyscanner] It should be safe to run this comman

[jira] [Commented] (KAFKA-6199) Single broker with fast growing heap usage

[ https://issues.apache.org/jira/browse/KAFKA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266985#comment-16266985 ] Manikumar commented on KAFKA-6199: -- Can you attach the output of of jmap command? {quote

[jira] [Commented] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260939#comment-16260939 ] Manikumar commented on KAFKA-5407: -- [~ijuma] Sure, I can work on it. But If i remember

[jira] [Commented] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244158#comment-16244158 ] Manikumar commented on KAFKA-6185: -- @ijuma Heap histogram is also contains large number

[jira] [Commented] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243434#comment-16243434 ] Manikumar commented on KAFKA-6185: -- Can we take periodic output of the below given jmap c

[jira] [Assigned] (KAFKA-5647) Use async ZookeeperClient for Admin operations

[ https://issues.apache.org/jira/browse/KAFKA-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-5647: Assignee: Manikumar > Use async ZookeeperClient for Admin operations >

[jira] [Resolved] (KAFKA-2995) in 0.9.0.0 Old Consumer's commitOffsets with specify partition can submit not exists topic and partition to zk

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

[jira] [Resolved] (KAFKA-2062) Sync Producer, Variable Message Length, Multiple Threads = Direct memory overuse

[ https://issues.apache.org/jira/browse/KAFKA-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2062. -- Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-1958) ZookeeperConsumerConnector doesn't remove consumer node on shutdown.

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

[jira] [Resolved] (KAFKA-1415) Async producer.send can block forever if async.ProducerSendThread dies

[ https://issues.apache.org/jira/browse/KAFKA-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1415. -- Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-1066) Reduce logging on producer connection failures

[ https://issues.apache.org/jira/browse/KAFKA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1066. -- Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported > Reduce loggin

[jira] [Resolved] (KAFKA-1006) Consumer loses messages of a new topic with auto.offset.reset = largest

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

[jira] [Resolved] (KAFKA-610) connect.timeout.ms seems to do the wrong thing in the producer

[ https://issues.apache.org/jira/browse/KAFKA-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-610. - Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported. > connect.timeo

[jira] [Resolved] (KAFKA-599) SimpleConsumerShell ONLY connects to the first host in the broker-list string to fetch topic metadata

[ https://issues.apache.org/jira/browse/KAFKA-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-599. - Resolution: Auto Closed The Scala consumers are no longer supported. > SimpleConsumerShell ONLY connects

[jira] [Resolved] (KAFKA-435) Keep track of the transient test failure for Kafka-343 on Apache Jenkins

[ https://issues.apache.org/jira/browse/KAFKA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-435. - Resolution: Cannot Reproduce Closing inactive issue. > Keep track of the transient test failure for Kafka-

<    3   4   5   6   7   8   9   10   11   >