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

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

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

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

[jira] [Assigned] (KAFKA-3073) KafkaConnect should support regular expression for topics

[ https://issues.apache.org/jira/browse/KAFKA-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Klukas reassigned KAFKA-3073: -- Assignee: Jeff Klukas (was: Liquan Pei) > KafkaConnect should support regular expression for t

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16223707#comment-16223707 ] Dana Powers commented on KAFKA-3550: Does not happen on brokers 0.10+ . Feel free to r

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

[ https://issues.apache.org/jira/browse/KAFKA-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223701#comment-16223701 ] ASF GitHub Bot commented on KAFKA-5645: --- GitHub user omkreddy opened a pull request:

[jira] [Commented] (KAFKA-5060) Offset not found while broker is rebuilding its index after an index corruption

[ https://issues.apache.org/jira/browse/KAFKA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223661#comment-16223661 ] Ismael Juma commented on KAFKA-5060: Just to be clear, are both of you reporting the s

[jira] [Commented] (KAFKA-5060) Offset not found while broker is rebuilding its index after an index corruption

[ https://issues.apache.org/jira/browse/KAFKA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223653#comment-16223653 ] Spiros Ioannou commented on KAFKA-5060: --- Hi Romaric, you're right, it happened to u

[jira] [Resolved] (KAFKA-6061) "ERROR Error while electing or becoming leader on broker 13 (kafka.server.ZookeeperLeaderElector) kafka.common.KafkaException: Can't parse json string: null" should pri

[ https://issues.apache.org/jira/browse/KAFKA-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-6061. --- Resolution: Duplicate Fix Version/s: (was: 1.1.0) > "ERROR Error while electing or

[jira] [Commented] (KAFKA-3240) Replication issues

[ https://issues.apache.org/jira/browse/KAFKA-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223622#comment-16223622 ] Ismael Juma commented on KAFKA-3240: Does this happen with more recent versions? > Re

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16223620#comment-16223620 ] Ismael Juma commented on KAFKA-3550: [~dana.powers], does this still happen with newer

[jira] [Updated] (KAFKA-3359) Parallel log-recovery of un-flushed segments on startup

[ https://issues.apache.org/jira/browse/KAFKA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3359: --- Affects Version/s: (was: 0.9.0.1) (was: 0.8.2.2)

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

[ https://issues.apache.org/jira/browse/KAFKA-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223618#comment-16223618 ] Ismael Juma commented on KAFKA-3657: It would be good to know if anyone has seen this

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

[ https://issues.apache.org/jira/browse/KAFKA-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3657: --- Labels: reliability (was: ) > NewProducer NullPointerException on ProduceRequest > --

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

[ https://issues.apache.org/jira/browse/KAFKA-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3657: --- Affects Version/s: 0.9.0.1 > NewProducer NullPointerException on ProduceRequest >

[jira] [Resolved] (KAFKA-3756) javadoc has issues with incorrect @param, @throws, @return

[ https://issues.apache.org/jira/browse/KAFKA-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3756. Resolution: Auto Closed Closing as 0.8.2 branch is no longer supported. > javadoc has issues with i

[jira] [Resolved] (KAFKA-3860) No broker partitions consumed by consumer thread

[ https://issues.apache.org/jira/browse/KAFKA-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3860. Resolution: Auto Closed The old consumer is no longer supported, please upgrade to the Java consumer

[jira] [Resolved] (KAFKA-3917) Some __consumer_offsets replicas grow way too big

[ https://issues.apache.org/jira/browse/KAFKA-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3917. Resolution: Duplicate This log cleaner issue has been fixed in more recent versions. I suggest upgr

[jira] [Updated] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3955: --- Affects Version/s: (was: 0.9.0.1) (was: 0.8.2.2)

[jira] [Commented] (KAFKA-4083) ReassignPartitionsCommand does not check replication factor

[ https://issues.apache.org/jira/browse/KAFKA-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223613#comment-16223613 ] Ismael Juma commented on KAFKA-4083: This says "Patch Available", but there's no link

[jira] [Updated] (KAFKA-4040) Round Robin Assignment does not create balanced assignments

[ https://issues.apache.org/jira/browse/KAFKA-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4040: --- Affects Version/s: (was: 0.8.2.2) 1.0.0 0.10.0.0

[jira] [Commented] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223612#comment-16223612 ] Ismael Juma commented on KAFKA-4084: [~tcrayford-heroku], can you please answer Jun's

[jira] [Resolved] (KAFKA-4096) Kafka Backup and Recovery

[ https://issues.apache.org/jira/browse/KAFKA-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4096. Resolution: Auto Closed Thanks for the JIRA. This should work. If you are still seeing this with a m

[jira] [Commented] (KAFKA-4128) Kafka broker losses messages when zookeeper session times out

[ https://issues.apache.org/jira/browse/KAFKA-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223606#comment-16223606 ] Ismael Juma commented on KAFKA-4128: Any chance you could test with a more recent vers

[jira] [Assigned] (KAFKA-4203) Java producer default max message size does not align with broker default

[ https://issues.apache.org/jira/browse/KAFKA-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4203: -- Assignee: Ismael Juma (was: Grant Henke) > Java producer default max message size does not ali

[jira] [Commented] (KAFKA-4203) Java producer default max message size does not align with broker default

[ https://issues.apache.org/jira/browse/KAFKA-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223603#comment-16223603 ] Ismael Juma commented on KAFKA-4203: Since this is a trivial issue and has been there

[jira] [Updated] (KAFKA-4203) Java producer default max message size does not align with broker default

[ https://issues.apache.org/jira/browse/KAFKA-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4203: --- Priority: Major (was: Critical) > Java producer default max message size does not align with broker d

[jira] [Updated] (KAFKA-4203) Java producer default max message size does not align with broker default

[ https://issues.apache.org/jira/browse/KAFKA-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4203: --- Fix Version/s: 1.1.0 > Java producer default max message size does not align with broker default > ---

[jira] [Commented] (KAFKA-4203) Java producer default max message size does not align with broker default

[ https://issues.apache.org/jira/browse/KAFKA-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223601#comment-16223601 ] ASF GitHub Bot commented on KAFKA-4203: --- GitHub user ijuma opened a pull request:

[jira] [Updated] (KAFKA-4545) tombstone needs to be removed after delete.retention.ms has passed after it has been cleaned

[ https://issues.apache.org/jira/browse/KAFKA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4545: --- Affects Version/s: (was: 0.8.2.0) 1.0.0 0.10.0.0

[jira] [Updated] (KAFKA-4546) a consumer could miss tombstone when leader changes during the reads

[ https://issues.apache.org/jira/browse/KAFKA-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4546: --- Affects Version/s: (was: 0.8.2.1) 1.0.0 0.10.0.0

[jira] [Resolved] (KAFKA-4832) kafka producer send Async message to the wrong IP cannot to stop producer.close()

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

[jira] [Updated] (KAFKA-5801) Use hadoop.security.auth_to_local if available

[ https://issues.apache.org/jira/browse/KAFKA-5801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5801: --- Affects Version/s: (was: 0.10.2.0) (was: 0.9.0.1)

[jira] [Resolved] (KAFKA-5963) Null Pointer Exception on server

[ https://issues.apache.org/jira/browse/KAFKA-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5963. Resolution: Auto Closed Thanks for the JIRA. Kafka 0.8.x is no longer supported and the issue has mo

[jira] [Updated] (KAFKA-5801) Use hadoop.security.auth_to_local if available

[ https://issues.apache.org/jira/browse/KAFKA-5801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5801: --- Priority: Major (was: Critical) > Use hadoop.security.auth_to_local if available > --

[jira] [Resolved] (KAFKA-5981) Update the affected versions on bug KAFKA-1194

[ https://issues.apache.org/jira/browse/KAFKA-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5981. Resolution: Duplicate Updated the fix versions. Only included the ones that are still supported. >

[jira] [Updated] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1194: --- Affects Version/s: (was: 0.10.0.0, 0.11.0.0, 1.0.0) 1.0.0

[jira] [Updated] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1194: --- Affects Version/s: (was: 0.8.1) 0.10.0.0, 0.11.0.0, 1.0.0 > The kafka broke

[jira] [Resolved] (KAFKA-6043) Kafka 8.1.1 - .ZookeeperConsumerConnector.shutdown(ZookeeperConsumerConnector.scala:110) blocked

[ https://issues.apache.org/jira/browse/KAFKA-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6043. Resolution: Auto Closed The old consumer is deprecated and no further changes are planned. Please u

[jira] [Resolved] (KAFKA-6117) One Broker down can't rejoin the cluster

[ https://issues.apache.org/jira/browse/KAFKA-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6117. Resolution: Auto Closed Thanks for the JIRA. 0.8.2.x is unsupported at this point. Newer releases ha

[jira] [Resolved] (KAFKA-5934) Cross build for scala 2.12

[ https://issues.apache.org/jira/browse/KAFKA-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5934. Resolution: Won't Fix Thanks for the JIRA and PR. 0.8.x is unsupported at this point and we don't i

[jira] [Resolved] (KAFKA-2156) Possibility to plug in custom MetricRegistry

[ https://issues.apache.org/jira/browse/KAFKA-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2156. Resolution: Auto Closed It's unlikely that we will do this for Yammer Metrics. Please file a separat

[jira] [Updated] (KAFKA-2179) no graceful nor fast way to shutdown every broker without killing them

[ https://issues.apache.org/jira/browse/KAFKA-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2179: --- Affects Version/s: (was: 0.8.1.2) 1.0.0 0.10.0.0

[jira] [Resolved] (KAFKA-2180) topics never create on brokers though it succeeds in tool and is in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2180. Resolution: Auto Closed Not enough information and very old so auto closing. > topics never create

[jira] [Resolved] (KAFKA-2222) Write "Input/output error" did not result in broker shutdown

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-. Resolution: Won't Fix The code changed dramatically since this was filed (the stacktrace doesn't eve

[jira] [Updated] (KAFKA-2192) Async producer is not async when not connected

[ https://issues.apache.org/jira/browse/KAFKA-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2192: --- Affects Version/s: (was: 0.8.1.2) (was: 0.8.1.1)

[jira] [Resolved] (KAFKA-6064) Cluster hung when the controller tried to delete a bunch of topics

[ https://issues.apache.org/jira/browse/KAFKA-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6064. Resolution: Auto Closed 0.8.2.1 is no longer supported. Many bugs related to topic deletion have bee

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

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

[jira] [Updated] (KAFKA-5060) Offset not found while broker is rebuilding its index after an index corruption

[ https://issues.apache.org/jira/browse/KAFKA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5060: --- Labels: reliability (was: ) > Offset not found while broker is rebuilding its index after an index >

[jira] [Commented] (KAFKA-6126) Reduce rebalance time by not checking if created topics are available

[ https://issues.apache.org/jira/browse/KAFKA-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223398#comment-16223398 ] ASF GitHub Bot commented on KAFKA-6126: --- Github user jeyhunkarimov closed the pull r

[jira] [Resolved] (KAFKA-6140) When running tests on kafka then such logs apper:

[ https://issues.apache.org/jira/browse/KAFKA-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel resolved KAFKA-6140. -- Resolution: Duplicate Duplicate of KAFKA-6141 > When running tests on kafka then such logs apper: > ---

[jira] [Commented] (KAFKA-6141) Errors logs when running integration/kafka/tools/MirrorMakerIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223393#comment-16223393 ] ASF GitHub Bot commented on KAFKA-6141: --- GitHub user Sammers21 opened a pull request

[jira] [Created] (KAFKA-6141) Errors logs when running integration/kafka/tools/MirrorMakerIntegrationTest

Pavel created KAFKA-6141: Summary: Errors logs when running integration/kafka/tools/MirrorMakerIntegrationTest Key: KAFKA-6141 URL: https://issues.apache.org/jira/browse/KAFKA-6141 Project: Kafka Is

[jira] [Created] (KAFKA-6140) When running tests on kafka then such logs apper:

Pavel created KAFKA-6140: Summary: When running tests on kafka then such logs apper: Key: KAFKA-6140 URL: https://issues.apache.org/jira/browse/KAFKA-6140 Project: Kafka Issue Type: Improvement