[jira] [Commented] (KAFKA-4544) Add system tests for delegation token based authentication

[ https://issues.apache.org/jira/browse/KAFKA-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16606206#comment-16606206 ] Manikumar commented on KAFKA-4544: -- [~asasvari] _>> Initially, I wanted to use console_consumer.py and

[jira] [Resolved] (KAFKA-4978) kafka.metrics.reporters missing from the documentation

[ https://issues.apache.org/jira/browse/KAFKA-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4978. -- Resolution: Duplicate Resolving as duplicated of KAFKA-5066 which will add docs for KafkaMetricsConfig

[jira] [Resolved] (KAFKA-2244) Document Kafka metrics configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2244. -- Resolution: Duplicate Resolving as duplicated of KAFKA-5066 which will add docs for KafkaMetricsConfig

[jira] [Resolved] (KAFKA-1833) OfflinePartitionLeaderSelector may return null leader when ISR and Assgined Broker have no common

[ https://issues.apache.org/jira/browse/KAFKA-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1833. -- Resolution: Auto Closed Closing as PartitionLeaderSelector class is removed/refactored. >

[jira] [Resolved] (KAFKA-6746) Allow ZK Znode configurable for Kafka broker

[ https://issues.apache.org/jira/browse/KAFKA-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6746. -- Resolution: Fixed Fixed via https://github.com/apache/kafka/pull/5358 > Allow ZK Znode configurable

[jira] [Comment Edited] (KAFKA-7154) Apache kafka getting shut down everytime it is started

[ https://issues.apache.org/jira/browse/KAFKA-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541672#comment-16541672 ] Manikumar edited comment on KAFKA-7154 at 7/12/18 1:48 PM: --- looks like you are

[jira] [Commented] (KAFKA-7154) Apache kafka getting shut down everytime it is started

[ https://issues.apache.org/jira/browse/KAFKA-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541672#comment-16541672 ] Manikumar commented on KAFKA-7154: -- looks like you are closing the terminal where server started. You

[jira] [Resolved] (KAFKA-2194) Produce request failure after Kafka + Zookeeper restart

[ https://issues.apache.org/jira/browse/KAFKA-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2194. -- Resolution: Auto Closed Closing inactive issue. Please reopen if the issue still exists in newer

[jira] [Commented] (KAFKA-7398) Transient test failure: SaslAuthenticatorFailureDelayTest.testInvalidPasswordSaslPlain

[ https://issues.apache.org/jira/browse/KAFKA-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610773#comment-16610773 ] Manikumar commented on KAFKA-7398: -- cc [~dhruvilshah] > Transient test failure: >

[jira] [Created] (KAFKA-7398) Transient test failure: SaslAuthenticatorFailureDelayTest.testInvalidPasswordSaslPlain

Manikumar created KAFKA-7398: Summary: Transient test failure: SaslAuthenticatorFailureDelayTest.testInvalidPasswordSaslPlain Key: KAFKA-7398 URL: https://issues.apache.org/jira/browse/KAFKA-7398

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

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

[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

[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=16397208#comment-16397208 ] Manikumar commented on KAFKA-4027: -- More details about similar exception are here:

[jira] [Updated] (KAFKA-6741) Transient test failure: SslTransportLayerTest.testNetworkThreadTimeRecorded

[ https://issues.apache.org/jira/browse/KAFKA-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-6741: - Description: debug logs: {code} [2018-04-03 14:51:33,365] DEBUG Added sensor with name

[jira] [Created] (KAFKA-6741) Transient test failure: SslTransportLayerTest.testNetworkThreadTimeRecorded

Manikumar created KAFKA-6741: Summary: Transient test failure: SslTransportLayerTest.testNetworkThreadTimeRecorded Key: KAFKA-6741 URL: https://issues.apache.org/jira/browse/KAFKA-6741 Project: Kafka

[jira] [Assigned] (KAFKA-6752) Unclean leader election metric no longer working

[ https://issues.apache.org/jira/browse/KAFKA-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-6752: Assignee: Manikumar > Unclean leader election metric no longer working >

[jira] [Resolved] (KAFKA-6413) ReassignPartitionsCommand#parsePartitionReassignmentData() should give better error message when JSON is malformed

[ https://issues.apache.org/jira/browse/KAFKA-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6413. -- Resolution: Duplicate Resolving as duplicate of KAFKA-6084. >

[jira] [Resolved] (KAFKA-1405) Global JSON.globalNumberParser screws up other libraries

[ https://issues.apache.org/jira/browse/KAFKA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1405. -- Resolution: Fixed Old Scala JSON usage is removed in new versions of Kafka > Global

[jira] [Resolved] (KAFKA-2302) Currently iterated chunk is not cleared during consumer shutdown

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

[jira] [Resolved] (KAFKA-1643) message.send.max.retries not respected when no brokers are up

[ https://issues.apache.org/jira/browse/KAFKA-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1643. -- Resolution: Auto Closed The Scala producers have been deprecated for a while and no further work is

[jira] [Updated] (KAFKA-2021) Consolidate test classes for KafkaConfig

[ https://issues.apache.org/jira/browse/KAFKA-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-2021: - Description: * We have kafka.server.KafkaConfigTest, KafkaConfigConfigDefTest and kafka.unit.KafkaTest

[jira] [Commented] (KAFKA-1786) implement a global configuration feature for brokers

[ https://issues.apache.org/jira/browse/KAFKA-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435598#comment-16435598 ] Manikumar commented on KAFKA-1786: -- looks like this requirement is covered in Dynamic Broker config

[jira] [Resolved] (KAFKA-4124) Handle disk failures gracefully

[ https://issues.apache.org/jira/browse/KAFKA-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4124. -- Resolution: Duplicate Some of these requirements are implemented in KIP-112/KIP-113. Pls raise new

[jira] [Resolved] (KAFKA-611) Migration tool and Mirror Maker ignore mirror.topics.whitelist in config

[ https://issues.apache.org/jira/browse/KAFKA-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-611. - Resolution: Auto Closed mirror.topics.whitelist/blacklist were part of old consumer. also these configs

[jira] [Resolved] (KAFKA-2339) broker becomes unavailable if bad data is passed through the protocol

[ https://issues.apache.org/jira/browse/KAFKA-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2339. -- Resolution: Cannot Reproduce Not able to reproduce on latest server. Please reopen if you think the

[jira] [Resolved] (KAFKA-2661) Add a unit test for disconnecting idle socket connections

[ https://issues.apache.org/jira/browse/KAFKA-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2661. -- Resolution: Fixed SelectorTest.testCloseConnectionInClosingState/testCloseOldestConnection tests

[jira] [Assigned] (KAFKA-6778) DescribeConfigs does not return error for non-existent topic

[ https://issues.apache.org/jira/browse/KAFKA-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-6778: Assignee: Manikumar > DescribeConfigs does not return error for non-existent topic >

[jira] [Resolved] (KAFKA-4347) outputStreamId in Kafka spout

[ https://issues.apache.org/jira/browse/KAFKA-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4347. -- Resolution: Invalid Looks like this is related to Apache Storm Kafka connector. Request you raise the

[jira] [Resolved] (KAFKA-2284) ConsumerRebalanceListener receives wrong type in partitionOwnership values

[ https://issues.apache.org/jira/browse/KAFKA-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2284. -- Resolution: Auto Closed The Scala consumers have been deprecated and no further work is planned, please

[jira] [Resolved] (KAFKA-4373) Kafka Consumer API jumping offsets

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

[jira] [Resolved] (KAFKA-4883) invalid client sasl.jaas.config triggers NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4883. -- Resolution: Fixed Assignee: Manikumar Fix Version/s: 1.2.0 > invalid client

[jira] [Commented] (KAFKA-6798) Kafka leader rebalance failures

[ https://issues.apache.org/jira/browse/KAFKA-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442656#comment-16442656 ] Manikumar commented on KAFKA-6798: -- It does look like zk session timeout issue. Not sure why happening

[jira] [Resolved] (KAFKA-3476) -Xloggc is not recognised by IBM java

[ https://issues.apache.org/jira/browse/KAFKA-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3476. -- Resolution: Won't Fix Closing this as we can export the GC values and performance opts. Please reopen

[jira] [Resolved] (KAFKA-5262) Can't find some consumer group information

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

[jira] [Resolved] (KAFKA-5287) Messages getting repeated in kafka

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

[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=16442490#comment-16442490 ] Manikumar commented on KAFKA-6335: -- [~Sonia] Can you give more details? Are you seeing test failure or an

[jira] [Resolved] (KAFKA-1716) hang during shutdown of ZookeeperConsumerConnector

[ https://issues.apache.org/jira/browse/KAFKA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1716. -- Resolution: Auto Closed Closing inactive issue. The Scala consumers have been deprecated and no further

[jira] [Commented] (KAFKA-5813) Unexpected unclean leader election due to leader/controller's unusual event handling order

[ https://issues.apache.org/jira/browse/KAFKA-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442343#comment-16442343 ] Manikumar commented on KAFKA-5813: -- This might have fixed in async zk controller changes. > Unexpected

[jira] [Commented] (KAFKA-6798) Kafka leader rebalance failures

[ https://issues.apache.org/jira/browse/KAFKA-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442861#comment-16442861 ] Manikumar commented on KAFKA-6798: -- Yes, rebalances are due to zookeeper disconnects. Since it is

[jira] [Commented] (KAFKA-6798) Kafka leader rebalance failures

[ https://issues.apache.org/jira/browse/KAFKA-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441972#comment-16441972 ] Manikumar commented on KAFKA-6798: -- ISR is set to empty if all replicas are out of sync and unclean

[jira] [Comment Edited] (KAFKA-6798) Kafka leader rebalance failures

[ https://issues.apache.org/jira/browse/KAFKA-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441972#comment-16441972 ] Manikumar edited comment on KAFKA-6798 at 4/18/18 6:43 AM: --- ISR is set to empty

[jira] [Resolved] (KAFKA-6107) SCRAM user add appears to fail if Kafka has never been started

[ https://issues.apache.org/jira/browse/KAFKA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6107. -- Resolution: Fixed Fix Version/s: 1.1.0 This was fixed in KafkaZkClient changes work. > SCRAM

[jira] [Commented] (KAFKA-6479) Broker file descriptor leak after consumer request timeout

[ https://issues.apache.org/jira/browse/KAFKA-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441366#comment-16441366 ] Manikumar commented on KAFKA-6479: -- One of the option is to adjust "connections.max.idle.ms" config

[jira] [Commented] (KAFKA-6404) OldConsumer FetchRequest apiVersion not match resulting in broker RequestHandler socket leak

[ https://issues.apache.org/jira/browse/KAFKA-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441820#comment-16441820 ] Manikumar commented on KAFKA-6404: -- SocketServer error handling is improved in KAFKA-5607. This must have

[jira] [Resolved] (KAFKA-6707) The default value for config of Type.LONG should be *L

[ https://issues.apache.org/jira/browse/KAFKA-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6707. -- Resolution: Fixed > The default value for config of Type.LONG should be *L >

[jira] [Resolved] (KAFKA-6702) Wrong className in LoggerFactory.getLogger method

[ https://issues.apache.org/jira/browse/KAFKA-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6702. -- Resolution: Fixed > Wrong className in LoggerFactory.getLogger method >

[jira] [Resolved] (KAFKA-6630) Speed up the processing of TopicDeletionStopReplicaResponseReceived events on the controller

[ https://issues.apache.org/jira/browse/KAFKA-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6630. -- Resolution: Fixed Fix Version/s: 1.2.0 > Speed up the processing of

[jira] [Resolved] (KAFKA-6716) discardChannel should be released in MockSelector#completeSend

[ https://issues.apache.org/jira/browse/KAFKA-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6716. -- Resolution: Fixed Fix Version/s: 1.2.0 > discardChannel should be released in

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

[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] [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=16405870#comment-16405870 ] Manikumar edited comment on KAFKA-6689 at 3/20/18 7:05 AM: --- These temp files

[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=16405870#comment-16405870 ] Manikumar commented on KAFKA-6689: -- There temp files will be deleted after file.delete.delay.ms (default:

[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

[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

[jira] [Resolved] (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:all-tabpanel ] Manikumar resolved KAFKA-6676. -- Resolution: Fixed Fix Version/s: 1.1.0 > System tests do not handle ZK chroot properly with

[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=16406717#comment-16406717 ] Manikumar commented on KAFKA-6682: -- Looks like this fixed in :

[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=16406717#comment-16406717 ] Manikumar edited comment on KAFKA-6682 at 3/20/18 5:14 PM: --- Looks like this

[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-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-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-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-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] [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-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-6705) producer.send() should not block due to metadata not available

[ https://issues.apache.org/jira/browse/KAFKA-6705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412512#comment-16412512 ] Manikumar commented on KAFKA-6705: -- Existing JIRA: KAFKA-3539 > producer.send() should not block due to

[jira] [Commented] (KAFKA-7090) Zookeeper client setting in server-properties

[ https://issues.apache.org/jira/browse/KAFKA-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526390#comment-16526390 ] Manikumar commented on KAFKA-7090: -- Kafka still uses Zookeeper 3.4 client dependency. Currently

[jira] [Created] (KAFKA-7117) Allow AclCommand to use AdminClient API

Manikumar created KAFKA-7117: Summary: Allow AclCommand to use AdminClient API Key: KAFKA-7117 URL: https://issues.apache.org/jira/browse/KAFKA-7117 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-7099) KafkaLog4jAppender - not sending any message with level DEBUG

[ https://issues.apache.org/jira/browse/KAFKA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7099. -- Resolution: Duplicate Resolving this as duplicate of  KAFKA-6415.  Please post your

[jira] [Comment Edited] (KAFKA-7099) KafkaLog4jAppender - not sending any message with level DEBUG

[ https://issues.apache.org/jira/browse/KAFKA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526195#comment-16526195 ] Manikumar edited comment on KAFKA-7099 at 6/28/18 10:29 AM: Resolving this as

[jira] [Commented] (KAFKA-7034) Remove the duplicated listTopics from Consumer

[ https://issues.apache.org/jira/browse/KAFKA-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526215#comment-16526215 ] Manikumar commented on KAFKA-7034: -- AdminClient.listTopics() gives the topic names and

[jira] [Commented] (KAFKA-7508) Kafka broker anonymous disconnected from Zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656854#comment-16656854 ] Manikumar commented on KAFKA-7508: -- [~sathish051] Please add Kafka and Java version details. Why is

[jira] [Commented] (KAFKA-7508) Kafka broker anonymous disconnected from Zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651985#comment-16651985 ] Manikumar commented on KAFKA-7508: -- [~sathish051] Exception message shows "java.lang.OutOfMemoryError".

[jira] [Comment Edited] (KAFKA-7579) System Test Failure - security_test.SecurityTest.test_client_ssl_endpoint_validation_failure

[ https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671733#comment-16671733 ] Manikumar edited comment on KAFKA-7579 at 11/1/18 3:15 PM: --- tests are passing

[jira] [Commented] (KAFKA-7579) System Test Failure - security_test.SecurityTest.test_client_ssl_endpoint_validation_failure

[ https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671733#comment-16671733 ] Manikumar commented on KAFKA-7579: -- tests are passing locally after increasing console consume timeout.

[jira] [Commented] (KAFKA-7579) System Test Failure - security_test.SecurityTest.test_client_ssl_endpoint_validation_failure

[ https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671607#comment-16671607 ] Manikumar commented on KAFKA-7579: -- This issue is related to KAFKA-7561 > System Test Failure - >

[jira] [Updated] (KAFKA-7579) System Test Failure - security_test.SecurityTest.test_client_ssl_endpoint_validation_failure

[ https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7579: - Fix Version/s: 2.0.2 > System Test Failure - >

[jira] [Assigned] (KAFKA-7353) Connect logs 'this' for anonymous inner classes

[ https://issues.apache.org/jira/browse/KAFKA-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7353: Assignee: Kevin Lafferty > Connect logs 'this' for anonymous inner classes >

[jira] [Assigned] (KAFKA-7519) Transactional Ids Left in Pending State by TransactionStateManager During Transactional Id Expiration Are Unusable

[ https://issues.apache.org/jira/browse/KAFKA-7519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7519: Assignee: Manikumar > Transactional Ids Left in Pending State by TransactionStateManager During

[jira] [Assigned] (KAFKA-7519) Transactional Ids Left in Pending State by TransactionStateManager During Transactional Id Expiration Are Unusable

[ https://issues.apache.org/jira/browse/KAFKA-7519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7519: Assignee: Bridger Howell (was: Manikumar) > Transactional Ids Left in Pending State by

[jira] [Assigned] (KAFKA-7316) Use of filter method in KTable.scala may result in StackOverflowError

[ https://issues.apache.org/jira/browse/KAFKA-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7316: Assignee: Joan Goyeau > Use of filter method in KTable.scala may result in StackOverflowError >

[jira] [Assigned] (KAFKA-7301) KTable to KTable join invocation does not resolve in Scala DSL

[ https://issues.apache.org/jira/browse/KAFKA-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7301: Assignee: Joan Goyeau > KTable to KTable join invocation does not resolve in Scala DSL >

[jira] [Assigned] (KAFKA-5891) Cast transformation fails if record schema contains timestamp field

[ https://issues.apache.org/jira/browse/KAFKA-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-5891: Assignee: Maciej Bryński > Cast transformation fails if record schema contains timestamp field >

[jira] [Commented] (KAFKA-7535) KafkaConsumer doesn't report records-lag if isolation.level is read_committed

[ https://issues.apache.org/jira/browse/KAFKA-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663595#comment-16663595 ] Manikumar commented on KAFKA-7535: -- As mentioned in the JIRA description, this only impacts consumer

[jira] [Resolved] (KAFKA-5462) Add a configuration for users to specify a template for building a custom principal name

[ https://issues.apache.org/jira/browse/KAFKA-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5462. -- Resolution: Fixed Fix Version/s: 2.2.0 > Add a configuration for users to specify a template

[jira] [Updated] (KAFKA-7535) KafkaConsumer doesn't report records-lag if isolation.level is read_committed

[ https://issues.apache.org/jira/browse/KAFKA-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7535: - Fix Version/s: (was: 2.0.2) (was: 2.1.1) 2.0.1 >

[jira] [Commented] (KAFKA-7547) Avoid relogin in kafka if connection is already established.

[ https://issues.apache.org/jira/browse/KAFKA-7547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665001#comment-16665001 ] Manikumar commented on KAFKA-7547: -- Since Kerberos ticket expiration times are typically short, repeated

[jira] [Commented] (KAFKA-7546) Java implementation for Authorizer

[ https://issues.apache.org/jira/browse/KAFKA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663494#comment-16663494 ] Manikumar commented on KAFKA-7546: -- You can check this implementaion:

[jira] [Updated] (KAFKA-7516) Client (Producer and/or Consumer) crashes during initialization on Android

[ https://issues.apache.org/jira/browse/KAFKA-7516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7516: - Fix Version/s: (was: 2.0.1) 2.2.0 > Client (Producer and/or Consumer) crashes

[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=16681900#comment-16681900 ] Manikumar commented on KAFKA-6584: -- [~pachilo] Yes > Session expiration concurrent with ZooKeeper

[jira] [Updated] (KAFKA-7313) StopReplicaRequest should attempt to remove future replica for the partition only if future replica exists

[ https://issues.apache.org/jira/browse/KAFKA-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7313: - Fix Version/s: (was: 2.0.1) 2.0.2 > StopReplicaRequest should attempt to remove

[jira] [Updated] (KAFKA-7579) System Test Failure - security_test.SecurityTest.test_client_ssl_endpoint_validation_failure

[ https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7579: - Priority: Major (was: Blocker) > System Test Failure - >

[jira] [Resolved] (KAFKA-7579) System Test Failure - security_test.SecurityTest.test_client_ssl_endpoint_validation_failure

[ https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7579. -- Resolution: Fixed Fix Version/s: 2.1.0 This is fixed via KAFKA-7561. > System Test Failure -

[jira] [Updated] (KAFKA-7561) Console Consumer - system test fails

[ https://issues.apache.org/jira/browse/KAFKA-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7561: - Fix Version/s: (was: 2.1.1) 2.1.0 > Console Consumer - system test fails >

[jira] [Updated] (KAFKA-7286) Loading offsets and group metadata hangs with large group metadata records

[ https://issues.apache.org/jira/browse/KAFKA-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7286: - Fix Version/s: 2.0.1 > Loading offsets and group metadata hangs with large group metadata records >

[jira] [Updated] (KAFKA-7126) Reduce number of rebalance for large consumer groups after a topic is created

[ https://issues.apache.org/jira/browse/KAFKA-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7126: - Fix Version/s: (was: 2.0.0) 2.0.1 > Reduce number of rebalance for large consumer

[jira] [Updated] (KAFKA-7559) ConnectStandaloneFileTest system tests do not pass

[ https://issues.apache.org/jira/browse/KAFKA-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7559: - Fix Version/s: (was: 2.0.1) 2.0.2 > ConnectStandaloneFileTest system tests do not

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