[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-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-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] [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-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] [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] [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] [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] [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] [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=16604711#comment-16604711 ] Manikumar commented on KAFKA-4544: -- [~asasvari] Thanks for taking this. I was planning to write a

[jira] [Resolved] (KAFKA-1950) Expose methods from SerializationTestUtils to all tests

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

[jira] [Resolved] (KAFKA-949) Integrate kafka into YARN

[ https://issues.apache.org/jira/browse/KAFKA-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-949. - Resolution: Resolved Resolving as duplicate of KAFKA-1754 > Integrate kafka into YARN >

[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] [Resolved] (KAFKA-6801) Restrict Consumer to fetch data from secure port only, and deny from non-secure port.

[ https://issues.apache.org/jira/browse/KAFKA-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6801. -- Resolution: Information Provided Closing as per above comment. > Restrict Consumer to fetch data

[jira] [Resolved] (KAFKA-5962) java.io.IOException: Map failed

[ https://issues.apache.org/jira/browse/KAFKA-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5962. -- Resolution: Fixed Closing as docs added in KAFKA-6343 > java.io.IOException: Map failed >

[jira] [Resolved] (KAFKA-1712) Excessive storage usage on newly added node

[ https://issues.apache.org/jira/browse/KAFKA-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1712. -- Resolution: Fixed Fixed via https://issues.apache.org/jira/browse/KAFKA-2511 > Excessive storage

[jira] [Resolved] (KAFKA-1665) controller state gets stuck in message after execute

[ https://issues.apache.org/jira/browse/KAFKA-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1665. -- Resolution: Auto Closed Closing inactive issue. Closing as per above comments. > controller state

[jira] [Resolved] (KAFKA-2127) Running TopicCommand --alter causes connection close/reset errors in kafka logs

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

[jira] [Resolved] (KAFKA-7291) kafka-console-consumer.sh waits on inexistent topic

[ https://issues.apache.org/jira/browse/KAFKA-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7291. -- Resolution: Fixed Fixed in newer versions. Yes, you need to upgrade to latest versions. >

[jira] [Assigned] (KAFKA-6789) Add retry logic in AdminClient requests

[ https://issues.apache.org/jira/browse/KAFKA-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-6789: Assignee: Manikumar > Add retry logic in AdminClient requests >

[jira] [Commented] (KAFKA-4321) Make client.id available to MetricReporter and (De)Serializers in clients

[ https://issues.apache.org/jira/browse/KAFKA-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594698#comment-16594698 ] Manikumar commented on KAFKA-4321: -- Passing client.id for MetricReporters is handled in KAFKA-6123 >

[jira] [Resolved] (KAFKA-2385) zookeeper-shell does not work

[ https://issues.apache.org/jira/browse/KAFKA-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2385. -- Resolution: Fixed Fixed in new zookeeper (3.4.7 +) versions > zookeeper-shell does not work >

[jira] [Resolved] (KAFKA-2238) KafkaMetricsConfig cannot be configured in broker (KafkaConfig)

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

[jira] [Resolved] (KAFKA-4065) Missing Property in ProducerConfig.java - KafkaProducer API 0.9.0.0

[ https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4065. -- Resolution: Auto Closed Closing inactive issue. It is highly unlikely to add this feature. >

[jira] [Resolved] (KAFKA-3369) Add unit-tests to the Metadata Cache

[ https://issues.apache.org/jira/browse/KAFKA-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3369. -- Resolution: Fixed Closing as per above comment. > Add unit-tests to the Metadata Cache >

[jira] [Resolved] (KAFKA-6309) add support for getting topic defaults from AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6309. -- Resolution: Fixed Closing as per above comment. We can use "describeConfigs(brokerResource, new

[jira] [Commented] (KAFKA-7314) MirrorMaker example in documentation does not work

[ https://issues.apache.org/jira/browse/KAFKA-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590472#comment-16590472 ] Manikumar commented on KAFKA-7314: -- As I mentioned above, this looks like Docker networking/DNS issue.

[jira] [Commented] (KAFKA-7314) MirrorMaker example in documentation does not work

[ https://issues.apache.org/jira/browse/KAFKA-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590342#comment-16590342 ] Manikumar commented on KAFKA-7314: -- We have unit/system tests to verify the basic mirrormaker scenarios.

[jira] [Resolved] (KAFKA-6314) Add a tool to delete kafka based consumer offsets for a given group

[ https://issues.apache.org/jira/browse/KAFKA-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6314. -- Resolution: Duplicate Resolving as duplicate of KAFKA-6275 > Add a tool to delete kafka based

[jira] [Commented] (KAFKA-7306) Ability for producer to push to topic on remote server via ELB name

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

[jira] [Commented] (KAFKA-7314) MirrorMaker example in documentation does not work

[ https://issues.apache.org/jira/browse/KAFKA-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589238#comment-16589238 ] Manikumar commented on KAFKA-7314: -- looks like both consumer/producer properties are pointing to same

[jira] [Commented] (KAFKA-7244) Add note about memory map kernel limits to documentation

[ https://issues.apache.org/jira/browse/KAFKA-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589156#comment-16589156 ] Manikumar commented on KAFKA-7244: -- latest docs updated via

[jira] [Resolved] (KAFKA-7279) partitionsFor implicitly creates topic for the existent topic

[ https://issues.apache.org/jira/browse/KAFKA-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7279. -- Resolution: Duplicate Resolving as duplicate of KAFKA-7320/KIP-361 > partitionsFor implicitly creates

[jira] [Commented] (KAFKA-7165) Error while creating ephemeral at /brokers/ids/BROKER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588600#comment-16588600 ] Manikumar commented on KAFKA-7165: -- [~pachilo] Please send a mail to dev mailing list for Jira access.

[jira] [Created] (KAFKA-7319) Add documentation for consumer group management

Manikumar created KAFKA-7319: Summary: Add documentation for consumer group management Key: KAFKA-7319 URL: https://issues.apache.org/jira/browse/KAFKA-7319 Project: Kafka Issue Type: Task

[jira] [Commented] (KAFKA-7303) Kafka client is stuck when specifying wrong brokers

[ https://issues.apache.org/jira/browse/KAFKA-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583944#comment-16583944 ] Manikumar commented on KAFKA-7303: -- I think  Kafka Streams API updated in

[jira] [Resolved] (KAFKA-5444) Producer.send() will hang 8+ hours

[ https://issues.apache.org/jira/browse/KAFKA-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5444. -- Resolution: Fixed Closing as per above comment. Please reopen if the issue still exists. >

[jira] [Assigned] (KAFKA-5690) kafka-acls command should be able to list per principal

[ https://issues.apache.org/jira/browse/KAFKA-5690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-5690: Assignee: Manikumar > kafka-acls command should be able to list per principal >

[jira] [Commented] (KAFKA-7303) Kafka client is stuck when specifying wrong brokers

[ https://issues.apache.org/jira/browse/KAFKA-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583730#comment-16583730 ] Manikumar commented on KAFKA-7303: -- This was fixed part of KAFKA-6979 / KIP-266 . Now we can use

[jira] [Resolved] (KAFKA-6224) Can not build Kafka 1.0.0 with gradle 3.2.1

[ https://issues.apache.org/jira/browse/KAFKA-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6224. -- Resolution: Cannot Reproduce Please reopen if the issue still exists. > Can not build Kafka 1.0.0

[jira] [Created] (KAFKA-7287) Set open ACL permissions for old consumer znode path

Manikumar created KAFKA-7287: Summary: Set open ACL permissions for old consumer znode path Key: KAFKA-7287 URL: https://issues.apache.org/jira/browse/KAFKA-7287 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-7257) --property (silently) fails when configuring SSL parameters

[ https://issues.apache.org/jira/browse/KAFKA-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7257. -- Resolution: Not A Problem > --property (silently) fails when configuring SSL parameters >

[jira] [Resolved] (KAFKA-6211) PartitionAssignmentState is protected whereas KafkaConsumerGroupService.describeGroup() returns PartitionAssignmentState Object

[ https://issues.apache.org/jira/browse/KAFKA-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6211. -- Resolution: Won't Fix Closing this in favour of AdminClient API.   > PartitionAssignmentState is

[jira] [Resolved] (KAFKA-6095) Error when displaying LAG information consumer partitions that use zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6095. -- Resolution: Auto Closed Closing as scala consumer related code/tools are removed from 2.0 release.

[jira] [Resolved] (KAFKA-6432) Lookup indices may cause unnecessary page fault

[ https://issues.apache.org/jira/browse/KAFKA-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6432. -- Resolution: Fixed Fix Version/s: 2.1.0 > Lookup indices may cause unnecessary page fault >

[jira] [Commented] (KAFKA-7248) Kafka creating topic with no leader. Issue started showing up after unkerberizing the cluster

[ https://issues.apache.org/jira/browse/KAFKA-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573666#comment-16573666 ] Manikumar commented on KAFKA-7248: -- Did you enable authorizer? If yes, you can try disabling the

[jira] [Resolved] (KAFKA-7247) A link to Apache BookKeeper project is broken

[ https://issues.apache.org/jira/browse/KAFKA-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7247. -- Resolution: Fixed Fix Version/s: 2.1.0 > A link to Apache BookKeeper project is broken >

[jira] [Commented] (KAFKA-7256) First started Kafka server & leader failure blocks consumers

[ https://issues.apache.org/jira/browse/KAFKA-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573637#comment-16573637 ] Manikumar commented on KAFKA-7256: -- I think this is due to replication factor of "__consumer_offsets"

[jira] [Commented] (KAFKA-7257) --property (silently) fails when configuring SSL parameters

[ https://issues.apache.org/jira/browse/KAFKA-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573612#comment-16573612 ] Manikumar commented on KAFKA-7257: -- To pass configs, we need to use  "--producer-property" or

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

Manikumar created KAFKA-7259: Summary: Remove deprecated ZKUtils usage from ZkSecurityMigrator Key: KAFKA-7259 URL: https://issues.apache.org/jira/browse/KAFKA-7259 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-7226) kafka-console-consumer.sh doesn't use security.protocol provided in config file

[ https://issues.apache.org/jira/browse/KAFKA-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7226. -- Resolution: Information Provided Closing the issue related to HDP Kafka distribution. >

[jira] [Resolved] (KAFKA-7083) maxTickMessages in ConsumerGroup option

[ https://issues.apache.org/jira/browse/KAFKA-7083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7083. -- Resolution: Information Provided Closing the issue related to node.js client. Please contact client

[jira] [Comment Edited] (KAFKA-7226) kafka-console-consumer.sh doesn't use security.protocol provided in config file

[ https://issues.apache.org/jira/browse/KAFKA-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565681#comment-16565681 ] Manikumar edited comment on KAFKA-7226 at 8/1/18 5:37 PM: -- looks like the issue

[jira] [Commented] (KAFKA-7226) kafka-console-consumer.sh doesn't use security.protocol provided in config file

[ https://issues.apache.org/jira/browse/KAFKA-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565681#comment-16565681 ] Manikumar commented on KAFKA-7226: -- looks like the issue is specific to HDP Kafka distribution. Can you

[jira] [Issue Comment Deleted] (KAFKA-7229) Failed to dynamically update kafka certificate in kafka 2.0.0

[ https://issues.apache.org/jira/browse/KAFKA-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7229: - Comment: was deleted (was: This may be due to the default value change for

[jira] [Commented] (KAFKA-7229) Failed to dynamically update kafka certificate in kafka 2.0.0

[ https://issues.apache.org/jira/browse/KAFKA-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565625#comment-16565625 ] Manikumar commented on KAFKA-7229: -- This may be due to the default value change for

[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=16564177#comment-16564177 ] Manikumar commented on KAFKA-5407: -- [~fvegaucr] I am not sure what is happening. It is very difficult

[jira] [Comment Edited] (KAFKA-7165) Error while creating ephemeral at /brokers/ids/BROKER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563458#comment-16563458 ] Manikumar edited comment on KAFKA-7165 at 7/31/18 10:46 AM: [~pachilo]   your

[jira] [Commented] (KAFKA-7165) Error while creating ephemeral at /brokers/ids/BROKER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563458#comment-16563458 ] Manikumar commented on KAFKA-7165: -- [~pachilo]   your solution may work, but we should be careful not to

[jira] [Created] (KAFKA-7210) Add system test for log compaction

Manikumar created KAFKA-7210: Summary: Add system test for log compaction Key: KAFKA-7210 URL: https://issues.apache.org/jira/browse/KAFKA-7210 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-4690) IllegalStateException using DeleteTopicsRequest when delete.topic.enable=false

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

[jira] [Resolved] (KAFKA-5799) New KafkaSpoutConfig(Scheme)-ByteArrayKeyValueScheme

[ https://issues.apache.org/jira/browse/KAFKA-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5799. -- Resolution: Auto Closed Closing Apache Storm - Kafka Spout related query.  If this still issue, please

[jira] [Commented] (KAFKA-5962) java.io.IOException: Map failed

[ https://issues.apache.org/jira/browse/KAFKA-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555738#comment-16555738 ] Manikumar commented on KAFKA-5962: -- some info here: https://issues.apache.org/jira/browse/KAFKA-6343 >

[jira] [Comment Edited] (KAFKA-2395) Linked to a interfaces even though the host.name had config

[ https://issues.apache.org/jira/browse/KAFKA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1610#comment-1610 ] Manikumar edited comment on KAFKA-2395 at 7/25/18 10:42 AM: extra port is

[jira] [Resolved] (KAFKA-2395) Linked to a interfaces even though the host.name had config

[ https://issues.apache.org/jira/browse/KAFKA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2395. -- Resolution: Not A Problem extra port is related to KAFKA-1869 > Linked to a interfaces even though

[jira] [Resolved] (KAFKA-2396) I have config host.name and advertised.host.name but still have a link connet to 0.0.0.0 with random port

[ https://issues.apache.org/jira/browse/KAFKA-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2396. -- Resolution: Not A Problem extra port is related to JMX. See  KAFKA-1869 > I have config host.name and

[jira] [Resolved] (KAFKA-2318) replica manager repeatedly tries to fetch from partitions already moved during controlled shutdown

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

[jira] [Resolved] (KAFKA-3040) Broker didn't report new data after change in leader

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

[jira] [Resolved] (KAFKA-2890) Strange behaviour during partitions reassignment.

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

[jira] [Resolved] (KAFKA-2968) Refactor ReplicaManager to be optimal for o.a.k.c requests

[ https://issues.apache.org/jira/browse/KAFKA-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2968. -- Resolution: Fixed Closing this as scala request/responses classes are removed and ReplicaManager is 

[jira] [Resolved] (KAFKA-2969) Refactor MetadataCache to be optimal for o.a.k.c requests

[ https://issues.apache.org/jira/browse/KAFKA-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2969. -- Resolution: Fixed Closing this as scala request/responses classes are removed and MetadataCache

[jira] [Resolved] (KAFKA-2075) Validate that all kafka.api requests has been removed and clean up compatibility code

[ https://issues.apache.org/jira/browse/KAFKA-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2075. -- Resolution: Fixed Old scala request/reponse classes are removed as part of KAFKA-2983: > Validate

[jira] [Commented] (KAFKA-6438) NSEE while concurrently creating and deleting a topic

[ https://issues.apache.org/jira/browse/KAFKA-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16553212#comment-16553212 ] Manikumar commented on KAFKA-6438: -- This might have been fixed in KAFKA-6630 cleanups.  > NSEE while

[jira] [Commented] (KAFKA-7165) Error while creating ephemeral at /brokers/ids/BROKER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16552098#comment-16552098 ] Manikumar commented on KAFKA-7165: -- [~pachilo]  I think we are waiting for  ZOOKEEPER-2985  fix.  If you

[jira] [Commented] (KAFKA-7165) Error while creating ephemeral at /brokers/ids/BROKER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551591#comment-16551591 ] Manikumar commented on KAFKA-7165: -- Looks like related to *KAFKA-6584* > Error while creating ephemeral

[jira] [Resolved] (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:all-tabpanel ] Manikumar resolved KAFKA-7154. -- Resolution: Information Provided > Apache kafka getting shut down everytime it is started >

[jira] [Resolved] (KAFKA-2008) Update num.consumer.fetchers description in Kafka documentation

[ https://issues.apache.org/jira/browse/KAFKA-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2008. -- Resolution: Auto Closed Closing issue related old consumer configs. Old consumer config doc section

[jira] [Resolved] (KAFKA-7081) Add describe all topics API to AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-7081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7081. -- Resolution: Won't Fix Closing this KIP in favor of adding filtering support to the Metadata API  

[jira] [Updated] (KAFKA-1420) Replace AdminUtils.createOrUpdateTopicPartitionAssignmentPathInZK with TestUtils.createTopic in unit tests

[ https://issues.apache.org/jira/browse/KAFKA-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-1420: - Fix Version/s: 2.1.0 > Replace AdminUtils.createOrUpdateTopicPartitionAssignmentPathInZK with >

[jira] [Resolved] (KAFKA-1420) Replace AdminUtils.createOrUpdateTopicPartitionAssignmentPathInZK with TestUtils.createTopic in unit tests

[ https://issues.apache.org/jira/browse/KAFKA-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1420. -- Resolution: Fixed Fixed as part of https://github.com/apache/kafka/pull/5303 > Replace

[jira] [Commented] (KAFKA-7184) Kafka is going down with issue ERROR Failed to clean up log for __consumer_offsets-0 in dir /tmp/kafkadev2-logs due to IOException (kafka.server.LogDirFailureChannel)

[ https://issues.apache.org/jira/browse/KAFKA-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16549186#comment-16549186 ] Manikumar commented on KAFKA-7184: -- looks like your data directory is in /tmp/ folder.  /tmp may get

[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] [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] [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] [Resolved] (KAFKA-3571) Traits for utilities like ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3571. -- Resolution: Won't Fix Now AdminClient has support for most of the admin API. This can be used for

[jira] [Resolved] (KAFKA-7123) Documentation: broken link http://confluent.io/docs/current/kafka-rest/docs/intro.html

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

[jira] [Commented] (KAFKA-7124) Number of AnyLogDir should match the length of the replicas list

[ https://issues.apache.org/jira/browse/KAFKA-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529073#comment-16529073 ] Manikumar commented on KAFKA-7124: -- There is no issue with code. mentioned code generates "any" for each

[jira] [Resolved] (KAFKA-4122) Consumer startup swallows DNS resolution exception and infinitely retries

[ https://issues.apache.org/jira/browse/KAFKA-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4122. -- Resolution: Duplicate Fixed under KAFKA-7111. > Consumer startup swallows DNS resolution exception

[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] [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] [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] [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] [Updated] (KAFKA-7091) AdminClient should handle FindCoordinatorResponse errors

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

[jira] [Commented] (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=16523849#comment-16523849 ] Manikumar commented on KAFKA-7099: -- Existing issue:  KAFKA-6415. This temporarily handled in  KAFKA-6415 

[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=16523849#comment-16523849 ] Manikumar edited comment on KAFKA-7099 at 6/26/18 3:10 PM: --- Existing issue:  

[jira] [Resolved] (KAFKA-7100) kafka.tools.GetOffsetShell with enable Kerberos Security on Kafka1.0

[ https://issues.apache.org/jira/browse/KAFKA-7100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7100. -- Resolution: Duplicate This is being tracked in KAFKA-5235. > kafka.tools.GetOffsetShell with enable

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