[jira] [Commented] (KAFKA-7080) WindowStoreBuilder incorrectly initializes CachingWindowStore

[ https://issues.apache.org/jira/browse/KAFKA-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681546#comment-16681546 ] Manikumar commented on KAFKA-7080: -- [~vvcephei]  [~guozhang] Can we create a separate JIRA for the part

[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=16681872#comment-16681872 ] Manikumar commented on KAFKA-6584: -- [~pachilo] maybe we can leave this as open, so that we can track

[jira] [Commented] (KAFKA-7274) Incorrect subject credential used in inter-broker communication

[ https://issues.apache.org/jira/browse/KAFKA-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638347#comment-16638347 ] Manikumar commented on KAFKA-7274: -- [~rsivaram] Thanks for the explanation. Let me know, if we need to

[jira] [Resolved] (KAFKA-7355) Topic Configuration Changes are not applied until reboot

[ https://issues.apache.org/jira/browse/KAFKA-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7355. -- Resolution: Duplicate Resolving as duplicate of KAFKA-7366. Raised a PR for KAFKA-7366.  > Topic

[jira] [Commented] (KAFKA-7463) ConsoleProducer rejects producer property values with equals signs

[ https://issues.apache.org/jira/browse/KAFKA-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634303#comment-16634303 ] Manikumar commented on KAFKA-7463: -- This might have fixed in KAFKA-7388. > ConsoleProducer rejects

[jira] [Resolved] (KAFKA-3601) fail fast when newer client connecting to older server

[ https://issues.apache.org/jira/browse/KAFKA-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3601. -- Resolution: Fixed Closing in favour of newer releases.  Please reopen if you think otherwise > fail

[jira] [Commented] (KAFKA-7274) Incorrect subject credential used in inter-broker communication

[ https://issues.apache.org/jira/browse/KAFKA-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638241#comment-16638241 ] Manikumar commented on KAFKA-7274: -- [~rsivaram] As described in the JIRA, incase of static JAAS

[jira] [Resolved] (KAFKA-7429) Enable dynamic key/truststore update with same filename/password

[ https://issues.apache.org/jira/browse/KAFKA-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7429. -- Resolution: Fixed > Enable dynamic key/truststore update with same filename/password >

[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=16599038#comment-16599038 ] Manikumar commented on KAFKA-4544: -- [~asasvari] If you are interested, Please takeover the JIRA.

[jira] [Commented] (KAFKA-7425) Kafka Broker -Unable to start

[ https://issues.apache.org/jira/browse/KAFKA-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16622562#comment-16622562 ] Manikumar commented on KAFKA-7425: -- looks like you have used Kafka 1.1+ release kafka-acls.sh script for

[jira] [Assigned] (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 reassigned KAFKA-5462: Assignee: Manikumar > Add a configuration for users to specify a template for building a custom

[jira] [Resolved] (KAFKA-2471) Replicas Order and Leader out of sync

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

[jira] [Assigned] (KAFKA-7216) Exception while running kafka-acls.sh from 1.0 env on target Kafka env with 1.1.1

[ https://issues.apache.org/jira/browse/KAFKA-7216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7216: Assignee: Manikumar > Exception while running kafka-acls.sh from 1.0 env on target Kafka env with

[jira] [Resolved] (KAFKA-7425) Kafka Broker -Unable to start

[ https://issues.apache.org/jira/browse/KAFKA-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7425. -- Resolution: Duplicate will handle this as part of KAFKA-7216. > Kafka Broker -Unable to start >

[jira] [Resolved] (KAFKA-5066) KafkaMetricsConfig properties and description notably missing from documentation

[ https://issues.apache.org/jira/browse/KAFKA-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5066. -- Resolution: Fixed > KafkaMetricsConfig properties and description notably missing from >

[jira] [Resolved] (KAFKA-3532) add principal.builder.class that can extract user from a field

[ https://issues.apache.org/jira/browse/KAFKA-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3532. -- Resolution: Duplicate This will be fixed be part of KAFKA-5462/KIP-371 > add principal.builder.class

[jira] [Assigned] (KAFKA-7466) Implement KIP-339: Create a new IncrementalAlterConfigs API

[ https://issues.apache.org/jira/browse/KAFKA-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7466: Assignee: Manikumar > Implement KIP-339: Create a new IncrementalAlterConfigs API >

[jira] [Commented] (KAFKA-7746) sasl.jaas.config dynamic broker configuration does not accept "=" in value

[ https://issues.apache.org/jira/browse/KAFKA-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723750#comment-16723750 ] Manikumar commented on KAFKA-7746: -- Can you try below format? {code} bin/kafka-configs.sh

[jira] [Resolved] (KAFKA-7742) DelegationTokenCache#hmacIdCache entry is not cleared when a token is removed using removeToken(String tokenId) API.

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

[jira] [Resolved] (KAFKA-7762) KafkaConsumer uses old API in the javadocs

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

[jira] [Assigned] (KAFKA-7762) KafkaConsumer uses old API in the javadocs

[ https://issues.apache.org/jira/browse/KAFKA-7762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7762: Assignee: Matthias Weßendorf > KafkaConsumer uses old API in the javadocs >

[jira] [Assigned] (KAFKA-7054) Kafka describe command should throw topic doesn't exist exception.

[ https://issues.apache.org/jira/browse/KAFKA-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7054: Assignee: Manohar Vanam > Kafka describe command should throw topic doesn't exist exception. >

[jira] [Resolved] (KAFKA-7054) Kafka describe command should throw topic doesn't exist exception.

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

[jira] [Resolved] (KAFKA-6149) LogCleanerManager should include topic partition name when warning of invalid cleaner offset

[ https://issues.apache.org/jira/browse/KAFKA-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6149. -- Resolution: Fixed Fix Version/s: 0.11.0.1 1.0.0 This was fixed in 1.0 and

[jira] [Commented] (KAFKA-7696) kafka-delegation-tokens.sh using a config file that contains security.protocol=SASL_PLAINTEXT throws OutOfMemoryError if it tries to connect to an SSL-enabled secured b

[ https://issues.apache.org/jira/browse/KAFKA-7696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708257#comment-16708257 ] Manikumar commented on KAFKA-7696: -- [~asasvari] This is related to KAFKA-4493. There is a WIP PR

[jira] [Commented] (KAFKA-7390) Enable the find-sec-bugs spotBugs plugin for Gradle

[ https://issues.apache.org/jira/browse/KAFKA-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706140#comment-16706140 ] Manikumar commented on KAFKA-7390: -- cc [~ijuma] > Enable the find-sec-bugs spotBugs plugin for Gradle >

[jira] [Created] (KAFKA-7694) Support ZooKeeper based master/secret key management for delegation tokens

Manikumar created KAFKA-7694: Summary: Support ZooKeeper based master/secret key management for delegation tokens Key: KAFKA-7694 URL: https://issues.apache.org/jira/browse/KAFKA-7694 Project: Kafka

[jira] [Resolved] (KAFKA-7617) Document security primitives

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

[jira] [Resolved] (KAFKA-7259) Remove deprecated ZKUtils usage from ZkSecurityMigrator

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

[jira] [Commented] (KAFKA-7390) Enable the find-sec-bugs spotBugs plugin for Gradle

[ https://issues.apache.org/jira/browse/KAFKA-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694262#comment-16694262 ] Manikumar commented on KAFKA-7390: -- [~timmy2702] I have given you Jira contributor permissions. Please

[jira] [Assigned] (KAFKA-7390) Enable the find-sec-bugs spotBugs plugin for Gradle

[ https://issues.apache.org/jira/browse/KAFKA-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7390: Assignee: (was: Manikumar) > Enable the find-sec-bugs spotBugs plugin for Gradle >

[jira] [Assigned] (KAFKA-7390) Enable the find-sec-bugs spotBugs plugin for Gradle

[ https://issues.apache.org/jira/browse/KAFKA-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-7390: Assignee: Manikumar > Enable the find-sec-bugs spotBugs plugin for Gradle >

[jira] [Updated] (KAFKA-7205) KafkaConsumer / KafkaProducer should allow Reconfiguration of SSL Configuration

[ https://issues.apache.org/jira/browse/KAFKA-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7205: - Labels: needs-kip (was: ) Yes, you can raise PR against trunk.  Since this is a public API change, we

[jira] [Resolved] (KAFKA-7554) zookeeper.session.timeout.ms Value

[ https://issues.apache.org/jira/browse/KAFKA-7554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7554. -- Resolution: Not A Problem Default Zookeeper session timeout value 6 seconds. If the server fails to

[jira] [Resolved] (KAFKA-7659) dummy test

[ https://issues.apache.org/jira/browse/KAFKA-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7659. -- Resolution: Invalid > dummy test > -- > > Key: KAFKA-7659 >

[jira] [Resolved] (KAFKA-7616) MockConsumer can return ConsumerRecords objects with a non-empty map but no records

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

[jira] [Resolved] (KAFKA-6971) Passing in help flag to kafka-console-producer should print arg options

[ https://issues.apache.org/jira/browse/KAFKA-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6971. -- Resolution: Duplicate > Passing in help flag to kafka-console-producer should print arg options >

[jira] [Commented] (KAFKA-7361) Kafka wont reconnect after NoRouteToHostException

[ https://issues.apache.org/jira/browse/KAFKA-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692035#comment-16692035 ] Manikumar commented on KAFKA-7361: -- This must be fixed in

[jira] [Resolved] (KAFKA-7323) add replication factor doesn't work

[ https://issues.apache.org/jira/browse/KAFKA-7323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7323. -- Resolution: Not A Problem Closing as per above comment. probably heap memory is not sufficient.

[jira] [Resolved] (KAFKA-764) Race Condition in Broker Registration after ZooKeeper disconnect

[ https://issues.apache.org/jira/browse/KAFKA-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-764. - Resolution: Duplicate This old issue is similar to KAFKA-7165. Closing this as duplicate KAFKA-7165 >

[jira] [Resolved] (KAFKA-5994) Improve transparency of broker user ACL misconfigurations

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

[jira] [Assigned] (KAFKA-5994) Improve transparency of broker user ACL misconfigurations

[ https://issues.apache.org/jira/browse/KAFKA-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-5994: Assignee: Manikumar > Improve transparency of broker user ACL misconfigurations >

[jira] [Resolved] (KAFKA-7752) zookeeper-security-migration.sh does not remove ACL on kafka-acl-extended

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

[jira] [Resolved] (KAFKA-7781) Add validation check for Topic retention.ms property

[ https://issues.apache.org/jira/browse/KAFKA-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7781. -- Resolution: Fixed Assignee: Kamal Chandraprakash Fix Version/s: 2.2.0 > Add validation

[jira] [Resolved] (KAFKA-2139) Add a separate controller messge queue with higher priority on broker side

[ https://issues.apache.org/jira/browse/KAFKA-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2139. -- Resolution: Duplicate Closing this in-favor of KAFKA-4453/KIP-291. > Add a separate controller messge

[jira] [Resolved] (KAFKA-1825) leadership election state is stale and never recovers without all brokers restarting

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

[jira] [Resolved] (KAFKA-2219) reassign partition fails with offset 0 being asked for but obviously not there

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

[jira] [Resolved] (KAFKA-1509) Restart of destination broker after unreplicated partition move leaves partitions without leader

[ https://issues.apache.org/jira/browse/KAFKA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1509. -- Resolution: Auto Closed Not able reproduce on new versions. might have fixed in newer versions. Please

[jira] [Resolved] (KAFKA-5789) Deleted topic is recreated when consumer subscribe the deleted one

[ https://issues.apache.org/jira/browse/KAFKA-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5789. -- Resolution: Duplicate Resolving as duplicate of KAFKA-7320/KIP-361 > Deleted topic is recreated when

[jira] [Resolved] (KAFKA-7388) An equal sign in a property value causes the broker to fail

[ https://issues.apache.org/jira/browse/KAFKA-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7388. -- Resolution: Fixed Fix Version/s: 2.1.0 > An equal sign in a property value causes the broker to

[jira] [Resolved] (KAFKA-3657) NewProducer NullPointerException on ProduceRequest

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

[jira] [Resolved] (KAFKA-4030) Update older quickstart documents to clarify which version they relate to

[ https://issues.apache.org/jira/browse/KAFKA-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4030. -- Resolution: Not A Problem Closing as per PR comment. > Update older quickstart documents to clarify

[jira] [Resolved] (KAFKA-4910) kafka consumer not receiving messages

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

[jira] [Commented] (KAFKA-7422) Huge memory consumption (leak?) by Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620453#comment-16620453 ] Manikumar commented on KAFKA-7422: -- I don't see any object leak in the thread dump.  I can see

[jira] [Resolved] (KAFKA-8090) Replace ControlledShutdown request/response with automated protocol

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

[jira] [Commented] (KAFKA-8196) Replace InitProducerId request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-8196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811077#comment-16811077 ] Manikumar commented on KAFKA-8196: -- https://github.com/apache/kafka/pull/6538/ > Replace

[jira] [Resolved] (KAFKA-7997) Replace SaslAuthenticate request/response with automated protocol

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

[jira] [Commented] (KAFKA-7982) ConcurrentModificationException and Continuous warnings "Attempting to send response via channel for which there is no open connection"

[ https://issues.apache.org/jira/browse/KAFKA-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776537#comment-16776537 ] Manikumar commented on KAFKA-7982: -- [~xabhi] Can you give us more details about deployment and Jaas

[jira] [Resolved] (KAFKA-7972) Replace SaslHandshake request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-7972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7972. -- Resolution: Fixed Fix Version/s: 2.3.0 > Replace SaslHandshake request/response with automated

[jira] [Resolved] (KAFKA-7832) Use automatic RPC generation in CreateTopics

[ https://issues.apache.org/jira/browse/KAFKA-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7832. -- Resolution: Fixed Fix Version/s: 2.3.0 > Use automatic RPC generation in CreateTopics >

[jira] [Created] (KAFKA-8044) System Test Failure: ReassignPartitionsTest.test_reassign_partitions

Manikumar created KAFKA-8044: Summary: System Test Failure: ReassignPartitionsTest.test_reassign_partitions Key: KAFKA-8044 URL: https://issues.apache.org/jira/browse/KAFKA-8044 Project: Kafka

[jira] [Resolved] (KAFKA-7312) Transient failure in kafka.api.AdminClientIntegrationTest.testMinimumRequestTimeouts

[ https://issues.apache.org/jira/browse/KAFKA-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7312. -- Resolution: Fixed Fix Version/s: (was: 2.3.0) 2.1.2

[jira] [Updated] (KAFKA-7312) Transient failure in kafka.api.AdminClientIntegrationTest.testMinimumRequestTimeouts

[ https://issues.apache.org/jira/browse/KAFKA-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7312: - Fix Version/s: (was: 2.2.0) 2.2.1 2.3.0 > Transient failure in

[jira] [Resolved] (KAFKA-7651) Flaky test SaslSslAdminClientIntegrationTest.testMinimumRequestTimeouts

[ https://issues.apache.org/jira/browse/KAFKA-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7651. -- Resolution: Fixed Fix Version/s: 2.2.1 2.1.2 2.0.2 This

[jira] [Commented] (KAFKA-7925) Constant 100% cpu usage by all kafka brokers

[ https://issues.apache.org/jira/browse/KAFKA-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781349#comment-16781349 ] Manikumar commented on KAFKA-7925: -- You can use  below steps to checkout the PR. {quote}git clone

[jira] [Commented] (KAFKA-8030) Flaky Test TopicCommandWithAdminClientTest#testDescribeUnderMinIsrPartitionsMixed

[ https://issues.apache.org/jira/browse/KAFKA-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782757#comment-16782757 ] Manikumar commented on KAFKA-8030: -- cc [~viktorsomogyi] > Flaky Test >

[jira] [Resolved] (KAFKA-8044) System Test Failure: ReassignPartitionsTest.test_reassign_partitions

[ https://issues.apache.org/jira/browse/KAFKA-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8044. -- Resolution: Fixed This was fixed in KAFKA-8061. Closing this issue for now. Will reopen the issue, If

[jira] [Resolved] (KAFKA-8117) Flaky Test DelegationTokenEndToEndAuthorizationTest#testNoProduceWithDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8117. -- Resolution: Duplicate Fix Version/s: (was: 2.3.0) > Flaky Test >

[jira] [Resolved] (KAFKA-7801) TopicCommand should not be able to alter transaction topic partition count

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

[jira] [Resolved] (KAFKA-7922) Returned authorized operations in describe responses (KIP-430)

[ https://issues.apache.org/jira/browse/KAFKA-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7922. -- Resolution: Fixed Fix Version/s: 2.3.0 > Returned authorized operations in describe responses

[jira] [Resolved] (KAFKA-7939) Flaky Test KafkaAdminClientTest#testCreateTopicsRetryBackoff

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

[jira] [Created] (KAFKA-8061) Use forceClose flag to check in the loop inside maybeWaitForProducerId.

Manikumar created KAFKA-8061: Summary: Use forceClose flag to check in the loop inside maybeWaitForProducerId. Key: KAFKA-8061 URL: https://issues.apache.org/jira/browse/KAFKA-8061 Project: Kafka

[jira] [Commented] (KAFKA-8044) System Test Failure: ReassignPartitionsTest.test_reassign_partitions

[ https://issues.apache.org/jira/browse/KAFKA-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786563#comment-16786563 ] Manikumar commented on KAFKA-8044: -- Underlying issue for this test failure is KAFKA-8061. As I have seen

[jira] [Resolved] (KAFKA-8018) Flaky Test SaslSslAdminClientIntegrationTest#testLegacyAclOpsNeverAffectOrReturnPrefixed

[ https://issues.apache.org/jira/browse/KAFKA-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8018. -- Resolution: Fixed > Flaky Test >

[jira] [Updated] (KAFKA-8061) Handle ProducerId reset while closing Sender thread.

[ https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-8061: - Summary: Handle ProducerId reset while closing Sender thread. (was: Use forceClose flag to check in the

[jira] [Updated] (KAFKA-8061) Handle concurrent ProducerId reset and call to Sender thread shutdown

[ https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-8061: - Summary: Handle concurrent ProducerId reset and call to Sender thread shutdown (was: Handle concurrent

[jira] [Updated] (KAFKA-8061) Handle concurrent ProducerId reset while closing Sender thread.

[ https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-8061: - Summary: Handle concurrent ProducerId reset while closing Sender thread. (was: Handle ProducerId reset

[jira] [Updated] (KAFKA-8061) Use forceClose flag to check in the loop inside maybeWaitForProducerId.

[ https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-8061: - Description: In KAFKA-5503, we have added a check (https://github.com/apache/kafka/pull/5881) for

[jira] [Updated] (KAFKA-8061) Handle ProducerId reset while closing Sender thread.

[ https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-8061: - Description: In KAFKA-5503, we have added a check (https://github.com/apache/kafka/pull/5881) for

[jira] [Resolved] (KAFKA-7978) Flaky Test SaslSslAdminClientIntegrationTest#testConsumerGroups

[ https://issues.apache.org/jira/browse/KAFKA-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7978. -- Resolution: Duplicate Resolving as duplicate of KAFKA-8098. Feel free to reopen the issue, If occurs

[jira] [Resolved] (KAFKA-8098) Flaky Test AdminClientIntegrationTest#testConsumerGroups

[ https://issues.apache.org/jira/browse/KAFKA-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8098. -- Resolution: Fixed Fix Version/s: 2.2.1 > Flaky Test

[jira] [Commented] (KAFKA-8106) Remove unnecessary decompression operation when logValidator do validation.

[ https://issues.apache.org/jira/browse/KAFKA-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795714#comment-16795714 ] Manikumar commented on KAFKA-8106: -- [~Flower.min] Instructions for the submitting code changes are

[jira] [Commented] (KAFKA-7898) ERROR Caught unexpected throwable (org.apache.zookeeper.ClientCnxn)

[ https://issues.apache.org/jira/browse/KAFKA-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794176#comment-16794176 ] Manikumar commented on KAFKA-7898: -- [~steven-usabilla] I think it is good to have fix in 2.1 branch as

[jira] [Resolved] (KAFKA-8060) The Kafka protocol generator should allow null default values for strings

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

[jira] [Resolved] (KAFKA-7799) Fix flaky test RestServerTest.testCORSEnabled

[ https://issues.apache.org/jira/browse/KAFKA-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7799. -- Resolution: Fixed Fix Version/s: 2.3.0 > Fix flaky test RestServerTest.testCORSEnabled >

[jira] [Resolved] (KAFKA-7896) Add some Log4J Kafka Properties for Producing to Secured Brokers

[ https://issues.apache.org/jira/browse/KAFKA-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7896. -- Resolution: Fixed Fix Version/s: 2.3.0 > Add some Log4J Kafka Properties for Producing to

[jira] [Reopened] (KAFKA-7799) Fix flaky test RestServerTest.testCORSEnabled

[ https://issues.apache.org/jira/browse/KAFKA-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reopened KAFKA-7799: -- This test is failing frequently on Jenkins builds. Reopening. > Fix flaky test

[jira] [Commented] (KAFKA-8032) Flaky Test UserQuotaTest#testQuotaOverrideDelete

[ https://issues.apache.org/jira/browse/KAFKA-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16819767#comment-16819767 ] Manikumar commented on KAFKA-8032: -- [~mjsax] Sorry for the delay. Will take a look next week. > Flaky

[jira] [Resolved] (KAFKA-7466) Implement KIP-339: Create a new IncrementalAlterConfigs API

[ https://issues.apache.org/jira/browse/KAFKA-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7466. -- Resolution: Fixed Reviewer: Colin P. McCabe Fix Version/s: 2.3.0 > Implement KIP-339:

[jira] [Resolved] (KAFKA-8461) Flakey test UncleanLeaderElectionTest#testUncleanLeaderElectionDisabledByTopicOverride

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

[jira] [Assigned] (KAFKA-8461) Flakey test UncleanLeaderElectionTest#testUncleanLeaderElectionDisabledByTopicOverride

[ https://issues.apache.org/jira/browse/KAFKA-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-8461: Assignee: Manikumar > Flakey test >

[jira] [Resolved] (KAFKA-8536) Error creating ACL Alter Topic in 2.2

[ https://issues.apache.org/jira/browse/KAFKA-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8536. -- Resolution: Fixed Assignee: Manikumar Fix Version/s: 2.1.2 2.0.2

[jira] [Resolved] (KAFKA-8390) Replace CreateDelegationToken request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-8390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8390. -- Resolution: Fixed Fix Version/s: 2.4.0 > Replace CreateDelegationToken request/response with

[jira] [Commented] (KAFKA-6945) Add support to allow users to acquire delegation tokens for other users

[ https://issues.apache.org/jira/browse/KAFKA-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872474#comment-16872474 ] Manikumar commented on KAFKA-6945: -- [~viktorsomogyi] Currently I am not working on this JIRA. Please

[jira] [Resolved] (KAFKA-3143) inconsistent state in ZK when all replicas are dead

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

[jira] [Resolved] (KAFKA-8152) Offline partition state not propagated by controller

[ https://issues.apache.org/jira/browse/KAFKA-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8152. -- Resolution: Duplicate > Offline partition state not propagated by controller >

[jira] [Commented] (KAFKA-8376) Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test.

[ https://issues.apache.org/jira/browse/KAFKA-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841208#comment-16841208 ] Manikumar commented on KAFKA-8376: -- [~viktorsomogyi] Can you check, if this is related to

[jira] [Created] (KAFKA-8376) Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test.

Manikumar created KAFKA-8376: Summary: Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test. Key: KAFKA-8376 URL: https://issues.apache.org/jira/browse/KAFKA-8376

[jira] [Comment Edited] (KAFKA-8376) Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test.

[ https://issues.apache.org/jira/browse/KAFKA-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841208#comment-16841208 ] Manikumar edited comment on KAFKA-8376 at 5/16/19 10:44 AM: [~viktorsomogyi]

[jira] [Resolved] (KAFKA-7455) JmxTool cannot connect to an SSL-enabled JMX RMI port

[ https://issues.apache.org/jira/browse/KAFKA-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7455. -- Resolution: Fixed Fix Version/s: 2.3.0 > JmxTool cannot connect to an SSL-enabled JMX RMI port

<    2   3   4   5   6   7   8   9   10   >