[jira] [Assigned] (KAFKA-4914) Partition re-assignment tool should check types before persisting state in ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-4914: Assignee: (was: Manikumar) > Partition re-assignment tool should check types before persisting

[jira] [Resolved] (KAFKA-5369) Producer hangs on metadata fetch from broker in security authorization related failures and no meaningful exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5369. -- Resolution: Duplicate Resolving this as duplicate of KAFKA-4764, KAFKA-5920 > Producer hangs on metad

[jira] [Commented] (KAFKA-4712) kafka-reassign-partitions causes ISR to shrink

[ https://issues.apache.org/jira/browse/KAFKA-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185754#comment-16185754 ] Manikumar commented on KAFKA-4712: -- This can be related to KAFKA-5758 > kafka-reassign-p

[jira] [Commented] (KAFKA-5997) acks=all does not seem to be honoured

[ https://issues.apache.org/jira/browse/KAFKA-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186974#comment-16186974 ] Manikumar commented on KAFKA-5997: -- We need to use min.insync.replicas to enforce durabi

[jira] [Commented] (KAFKA-5734) Heap (Old generation space) gradually increase

[ https://issues.apache.org/jira/browse/KAFKA-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187287#comment-16187287 ] Manikumar commented on KAFKA-5734: -- [~jangbora] looking at the metrics above, they are pe

[jira] [Comment Edited] (KAFKA-5734) Heap (Old generation space) gradually increase

[ https://issues.apache.org/jira/browse/KAFKA-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187287#comment-16187287 ] Manikumar edited comment on KAFKA-5734 at 10/1/17 6:02 AM: --- [~ja

[jira] [Created] (KAFKA-6005) Reject JoinGroup request from first member with empty protocol type/protocol list

Manikumar created KAFKA-6005: Summary: Reject JoinGroup request from first member with empty protocol type/protocol list Key: KAFKA-6005 URL: https://issues.apache.org/jira/browse/KAFKA-6005 Project: Kafk

[jira] [Commented] (KAFKA-6005) Reject JoinGroup request from first member with empty protocol type/protocol list

[ https://issues.apache.org/jira/browse/KAFKA-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189475#comment-16189475 ] Manikumar commented on KAFKA-6005: -- PR: https://github.com/apache/kafka/pull/3957 > Reje

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

[ https://issues.apache.org/jira/browse/KAFKA-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198271#comment-16198271 ] Manikumar commented on KAFKA-6022: -- looks like you are using old consumer API on mirror m

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

[ https://issues.apache.org/jira/browse/KAFKA-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198416#comment-16198416 ] Manikumar commented on KAFKA-6022: -- Since 0.10.1.0, no need to pass --new-consumer optio

[jira] [Commented] (KAFKA-6042) Kafka Request Handler deadlocks and brings down the cluster.

[ https://issues.apache.org/jira/browse/KAFKA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198453#comment-16198453 ] Manikumar commented on KAFKA-6042: -- This may be related KAFKA-5970 > Kafka Request Handl

[jira] [Commented] (KAFKA-6042) Kafka Request Handler deadlocks and brings down the cluster.

[ https://issues.apache.org/jira/browse/KAFKA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198497#comment-16198497 ] Manikumar commented on KAFKA-6042: -- It would we great if you can use KAFKA-5970 and valid

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

[ https://issues.apache.org/jira/browse/KAFKA-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199814#comment-16199814 ] Manikumar commented on KAFKA-6022: -- I think we missed to update consumer.properties file.

[jira] [Resolved] (KAFKA-4504) Details of retention.bytes property at Topic level are not clear on how they impact partition size

[ https://issues.apache.org/jira/browse/KAFKA-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4504. -- Resolution: Fixed Assignee: Manikumar Fix Version/s: 1.0.0 > Details of retention.bytes

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

[ https://issues.apache.org/jira/browse/KAFKA-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208881#comment-16208881 ] Manikumar commented on KAFKA-6077: -- Old consumer API is deprecated and will be removed in

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

[ https://issues.apache.org/jira/browse/KAFKA-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208881#comment-16208881 ] Manikumar edited comment on KAFKA-6077 at 10/18/17 6:52 AM: Ol

[jira] [Commented] (KAFKA-5978) Transient failure in SslTransportLayerTest.testNetworkThreadTimeRecorded

[ https://issues.apache.org/jira/browse/KAFKA-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209382#comment-16209382 ] Manikumar commented on KAFKA-5978: -- [~rsivaram] SslTransportLayerTest.testNetworkThreadT

[jira] [Assigned] (KAFKA-6071) Use ZookeeperClient in LogManager

[ https://issues.apache.org/jira/browse/KAFKA-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-6071: Assignee: Manikumar > Use ZookeeperClient in LogManager > -- > >

[jira] [Assigned] (KAFKA-6072) Use ZookeeperClient in GroupCoordinator and TransactionCoordinator

[ https://issues.apache.org/jira/browse/KAFKA-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-6072: Assignee: Manikumar > Use ZookeeperClient in GroupCoordinator and TransactionCoordinator >

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16212476#comment-16212476 ] Manikumar commented on KAFKA-6091: -- This behavior is changed in KAFKA-5547. > Authoriza

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=16212476#comment-16212476 ] Manikumar edited comment on KAFKA-6091 at 10/20/17 10:36 AM: -

[jira] [Assigned] (KAFKA-5645) Use async ZookeeperClient in SimpleAclAuthorizer

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

[jira] [Assigned] (KAFKA-5646) Use async ZookeeperClient for DynamicConfigManager

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

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

[ https://issues.apache.org/jira/browse/KAFKA-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223874#comment-16223874 ] Manikumar commented on KAFKA-6077: -- It is highly unlikely to accept patches for older cli

[jira] [Resolved] (KAFKA-6019) Sentry permissions bug on CDH

[ https://issues.apache.org/jira/browse/KAFKA-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6019. -- Resolution: Duplicate > Sentry permissions bug on CDH > - > >

[jira] [Resolved] (KAFKA-232) ConsumerConnector has no access to "getOffsetsBefore"

[ https://issues.apache.org/jira/browse/KAFKA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-232. - Resolution: Won't Fix Closing inactive issue. The old consumer is no longer supported. This jira requireme

[jira] [Resolved] (KAFKA-243) Improve consumer connector documentation to include blocking semantics of kafka message streams

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

[jira] [Resolved] (KAFKA-250) Provide consumer iterator callback handler

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

[jira] [Resolved] (KAFKA-242) Subsequent calls of ConsumerConnector.createMessageStreams cause Consumer offset to be incorrect

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

[jira] [Resolved] (KAFKA-853) Allow OffsetFetchRequest to initialize offsets

[ https://issues.apache.org/jira/browse/KAFKA-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-853. - Resolution: Won't Fix Closing inactive issue as per above comment. > Allow OffsetFetchRequest to initializ

[jira] [Resolved] (KAFKA-845) Re-implement shallow iteration on 0.8.1

[ https://issues.apache.org/jira/browse/KAFKA-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-845. - Resolution: Auto Closed Closing inactive issue. > Re-implement shallow iteration on 0.8.1 >

[jira] [Resolved] (KAFKA-810) KafkaStream toString method blocks indefinitely

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

[jira] [Resolved] (KAFKA-635) Producer error when trying to send not displayed unless in DEBUG logging level

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

[jira] [Resolved] (KAFKA-623) It should be possible to re-create KafkaStreams after an exception, without recreating ConsumerConnector

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

[jira] [Resolved] (KAFKA-602) A ConsumerConnector that never receives messages does not shutdown cleanly

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

[jira] [Resolved] (KAFKA-519) Allow commiting the state of single KafkaStream

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

[jira] [Resolved] (KAFKA-536) Kafka async appender/producer looses most messages

[ https://issues.apache.org/jira/browse/KAFKA-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-536. - Resolution: Auto Closed Closing inactive issue. > Kafka async appender/producer looses most messages > --

[jira] [Resolved] (KAFKA-601) ConsumerConnector.shutdown() hangs if autocommit is enabled, and no zk available

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

[jira] [Resolved] (KAFKA-788) Periodic refresh of topic metadata on the producer doesn't include all topics

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

[jira] [Resolved] (KAFKA-407) Uncaught InputStream.close() exception in CompressionUtils.compress()

[ https://issues.apache.org/jira/browse/KAFKA-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-407. - Resolution: Won't Fix This part of the code is removed. So closing the issue. > Uncaught InputStream.clos

[jira] [Resolved] (KAFKA-354) Refactor getter and setter API to conform to the new convention

[ https://issues.apache.org/jira/browse/KAFKA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-354. - Resolution: Won't Fix Closing inactive issue. > Refactor getter and setter API to conform to the new conve

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

[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-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-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-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-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-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-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-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] [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] [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] [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-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-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-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-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] [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=16270767#comment-16270767 ] Manikumar commented on KAFKA-6281: -- [~anilkumar...@gmail.com] 2mins is high value. increa

[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-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-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=16282116#comment-16282116 ] Manikumar commented on KAFKA-6199: -- [~rt_skyscanner] yes, jstack output > Single broker

[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-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-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] [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-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] [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-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] [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-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] [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-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] [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-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] [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] [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] [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-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] [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] [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-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] [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-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-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] [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] [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] [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-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] [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] [Resolved] (KAFKA-9612) CLI Dynamic Configuration with file input

[ https://issues.apache.org/jira/browse/KAFKA-9612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-9612. -- Fix Version/s: 2.6.0 Reviewer: Manikumar Resolution: Fixed > CLI Dynamic Configuration

[jira] [Resolved] (KAFKA-9034) kafka-run-class.sh will fail if JAVA_HOME has space

[ https://issues.apache.org/jira/browse/KAFKA-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-9034. -- Fix Version/s: 2.6.0 Resolution: Fixed Issue resolved by pull request 8481 [https://github.com/a

[jira] [Commented] (KAFKA-10592) system tests not running after python3 merge

[ https://issues.apache.org/jira/browse/KAFKA-10592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17218291#comment-17218291 ] Manikumar commented on KAFKA-10592: --- [~nizhikov]   Do we also need to update [vagrant

[jira] [Created] (KAFKA-10669) ListOffsetRequest: make CurrentLeaderEpoch field ignorable and set MaxNumOffsets field to 1

Manikumar created KAFKA-10669: - Summary: ListOffsetRequest: make CurrentLeaderEpoch field ignorable and set MaxNumOffsets field to 1 Key: KAFKA-10669 URL: https://issues.apache.org/jira/browse/KAFKA-10669

[jira] [Updated] (KAFKA-10669) ListOffsetRequest: make CurrentLeaderEpoch field ignorable and set MaxNumOffsets field to 1

[ https://issues.apache.org/jira/browse/KAFKA-10669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-10669: -- Description: Couple of failures observed after KAFKA-9627: Replace ListOffset request/response with a

[jira] [Resolved] (KAFKA-10669) ListOffsetRequest: make CurrentLeaderEpoch field ignorable and set MaxNumOffsets field to 1

[ https://issues.apache.org/jira/browse/KAFKA-10669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-10669. --- Resolution: Fixed Issue resolved by pull request 9540 [https://github.com/apache/kafka/pull/9540] >

[jira] [Assigned] (KAFKA-10669) ListOffsetRequest: make CurrentLeaderEpoch field ignorable and set MaxNumOffsets field to 1

[ https://issues.apache.org/jira/browse/KAFKA-10669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-10669: - Assignee: Manikumar > ListOffsetRequest: make CurrentLeaderEpoch field ignorable and set > Max

[jira] [Resolved] (KAFKA-12865) Documentation error for Admin Client API in describe ACLs

[ https://issues.apache.org/jira/browse/KAFKA-12865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-12865. --- Fix Version/s: 3.0.0 Resolution: Fixed > Documentation error for Admin Client API in describe

<    1   2   3   4   5   6   7   8   9   10   >