[jira] [Commented] (KAFKA-4950) ConcurrentModificationException when iterating over Kafka Metrics

[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148437#comment-16148437 ] Jean-Baptiste commented on KAFKA-4950: -- Hi, I was able to reproduce the issue using the following

[jira] [Commented] (KAFKA-5523) ReplayLogProducer not using the new Kafka consumer

[ https://issues.apache.org/jira/browse/KAFKA-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148423#comment-16148423 ] Guozhang Wang commented on KAFKA-5523: -- I think ReplayLogProducer is not deprecated. >

[jira] [Commented] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

[ https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148417#comment-16148417 ] Jeff Widman commented on KAFKA-3356: Is this waiting on anything to be merged? > Remove

[jira] [Updated] (KAFKA-5808) The Preferred Replica should be global and dynamic

[ https://issues.apache.org/jira/browse/KAFKA-5808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Canes Kelly updated KAFKA-5808: --- Description: When we create a topic in kafka, broker assigns replicas for partitions in this topic,

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

Allen Wang created KAFKA-5813: - Summary: Unexpected unclean leader election due to leader/controller's unusual event handling order Key: KAFKA-5813 URL: https://issues.apache.org/jira/browse/KAFKA-5813

[jira] [Commented] (KAFKA-5494) Idempotent producer should not require max.in.flight.requests.per.connection=1

[ https://issues.apache.org/jira/browse/KAFKA-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148186#comment-16148186 ] Apurva Mehta commented on KAFKA-5494: - I wrote up a short description of the solution's design here:

[jira] [Commented] (KAFKA-5812) Represent logDir with case class where absolute path is required

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

[jira] [Created] (KAFKA-5812) Represent logDir with case class where absolute path is required

Dong Lin created KAFKA-5812: --- Summary: Represent logDir with case class where absolute path is required Key: KAFKA-5812 URL: https://issues.apache.org/jira/browse/KAFKA-5812 Project: Kafka Issue

[jira] [Created] (KAFKA-5811) Trogdor should handle injecting disk faults

Colin P. McCabe created KAFKA-5811: -- Summary: Trogdor should handle injecting disk faults Key: KAFKA-5811 URL: https://issues.apache.org/jira/browse/KAFKA-5811 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-5476) Implement a system test that creates network partitions

[ https://issues.apache.org/jira/browse/KAFKA-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148074#comment-16148074 ] ASF GitHub Bot commented on KAFKA-5476: --- Github user cmccabe closed the pull request at:

[jira] [Updated] (KAFKA-5807) Check Connector.config() and Transformation.config() returns a valid ConfigDef

[ https://issues.apache.org/jira/browse/KAFKA-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Custenborder updated KAFKA-5807: --- Summary: Check Connector.config() and Transformation.config() returns a valid

[jira] [Updated] (KAFKA-5807) NPE on Connector.validate,

[ https://issues.apache.org/jira/browse/KAFKA-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Custenborder updated KAFKA-5807: --- Summary: NPE on Connector.validate, (was: NPE on Connector.validate) > NPE on

[jira] [Commented] (KAFKA-4107) Support offset reset capability in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148025#comment-16148025 ] Chris Riccomini commented on KAFKA-4107: :D > Support offset reset capability in Kafka Connect >

[jira] [Commented] (KAFKA-4107) Support offset reset capability in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147970#comment-16147970 ] Randall Hauch commented on KAFKA-4107: -- [~sliebau], have you made any progress on a KIP? Are you

[jira] [Commented] (KAFKA-1980) Console consumer throws OutOfMemoryError with large max-messages

[ https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147956#comment-16147956 ] Nick Dimiduk commented on KAFKA-1980: - Thanks! > Console consumer throws OutOfMemoryError with large

[jira] [Resolved] (KAFKA-4520) Kafka broker fails with not so user-friendly error msg when log.dirs is not set

[ https://issues.apache.org/jira/browse/KAFKA-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4520. -- Resolution: Fixed Fix Version/s: 0.11.0.0 > Kafka broker fails with not so user-friendly error

[jira] [Commented] (KAFKA-5763) Refactor NetworkClient to use LogContext

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

[jira] [Comment Edited] (KAFKA-5786) Yet another exception is causing that streamming app is zombie

[ https://issues.apache.org/jira/browse/KAFKA-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147838#comment-16147838 ] Matthias J. Sax edited comment on KAFKA-5786 at 8/30/17 7:02 PM: - Thanks

[jira] [Resolved] (KAFKA-5786) Yet another exception is causing that streamming app is zombie

[ https://issues.apache.org/jira/browse/KAFKA-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5786. Resolution: Duplicate > Yet another exception is causing that streamming app is zombie >

[jira] [Commented] (KAFKA-5786) Yet another exception is causing that streamming app is zombie

[ https://issues.apache.org/jira/browse/KAFKA-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147838#comment-16147838 ] Matthias J. Sax commented on KAFKA-5786: Thanks for the logs: If I read them correctly, some of

[jira] [Commented] (KAFKA-5779) Single message may exploit application based on KStream

[ https://issues.apache.org/jira/browse/KAFKA-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147756#comment-16147756 ] Matthias J. Sax commented on KAFKA-5779: You can set the timestamp extractor in the config of your

[jira] [Resolved] (KAFKA-270) sync producer / consumer test producing lot of kafka server exceptions & not getting the throughput mentioned here http://incubator.apache.org/kafka/performance.html

[ https://issues.apache.org/jira/browse/KAFKA-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-270. - Resolution: Won't Fix Closing due to inactivity. Pl reopen if you think the issue still exists > sync

[jira] [Resolved] (KAFKA-1492) Getting error when sending producer request at the broker end with a single broker

[ https://issues.apache.org/jira/browse/KAFKA-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1492. -- Resolution: Cannot Reproduce Pl reopen if you think the issue still exists > Getting error when

[jira] [Resolved] (KAFKA-1632) No such method error on KafkaStream.head

[ https://issues.apache.org/jira/browse/KAFKA-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1632. -- Resolution: Cannot Reproduce Mostly related to Kafka version mismatch. Pl reopen if you think the

[jira] [Resolved] (KAFKA-1463) producer fails with scala.tuple error

[ https://issues.apache.org/jira/browse/KAFKA-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1463. -- Resolution: Won't Fix Pl reopen if you think the issue still exists > producer fails with

[jira] [Resolved] (KAFKA-888) problems when shutting down the java consumer .

[ https://issues.apache.org/jira/browse/KAFKA-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-888. - Resolution: Cannot Reproduce Pl reopen if you think the issue still exists > problems when shutting

[jira] [Resolved] (KAFKA-1980) Console consumer throws OutOfMemoryError with large max-messages

[ https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1980. -- Resolution: Won't Fix [~ndimiduk] Agree. Updated the JIRA. > Console consumer throws OutOfMemoryError

[jira] [Reopened] (KAFKA-1980) Console consumer throws OutOfMemoryError with large max-messages

[ https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reopened KAFKA-1980: -- > Console consumer throws OutOfMemoryError with large max-messages >

[jira] [Commented] (KAFKA-1980) Console consumer throws OutOfMemoryError with large max-messages

[ https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147659#comment-16147659 ] Nick Dimiduk commented on KAFKA-1980: - Thanks for the explanation [~omkreddy]. Better to resolve this

[jira] [Commented] (KAFKA-5769) Transient test failure org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperationsWithZeroSizedCache

[ https://issues.apache.org/jira/browse/KAFKA-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147639#comment-16147639 ] Guozhang Wang commented on KAFKA-5769: -- This is resolved by KAFKA-5787, which has a patch for both

[jira] [Updated] (KAFKA-5787) StoreChangeLogReader needs to restore partitions that were added post initialization

[ https://issues.apache.org/jira/browse/KAFKA-5787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5787: - Fix Version/s: 1.0.0 > StoreChangeLogReader needs to restore partitions that were added post >

[jira] [Reopened] (KAFKA-5763) Refactor NetworkClient to use LogContext

[ https://issues.apache.org/jira/browse/KAFKA-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-5763: NetworkClient is a different class and it doesn't use LogContext yet. > Refactor NetworkClient to use

[jira] [Commented] (KAFKA-5763) Refactor NetworkClient to use LogContext

[ https://issues.apache.org/jira/browse/KAFKA-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147638#comment-16147638 ] Ismael Juma commented on KAFKA-5763: [~adyachkov], you can work on this, yes. Thanks! > Refactor

[jira] [Resolved] (KAFKA-5763) Refactor NetworkClient to use LogContext

[ https://issues.apache.org/jira/browse/KAFKA-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kamal Chandraprakash resolved KAFKA-5763. - Resolution: Fixed Fix Version/s: 1.0.0 [~ijuma] `ConsumerNetworkClient`

[jira] [Commented] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147598#comment-16147598 ] Nishant Jain commented on KAFKA-3894: - [~m...@vrischmann.me] I saw the exact same issue and realized

[jira] [Commented] (KAFKA-1980) Console consumer throws OutOfMemoryError with large max-messages

[ https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147595#comment-16147595 ] Manikumar commented on KAFKA-1980: -- [~ndimiduk] Apologies for not giving a proper explanation.

[jira] [Resolved] (KAFKA-5769) Transient test failure org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperationsWithZeroSizedCache

[ https://issues.apache.org/jira/browse/KAFKA-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5769. --- Resolution: Duplicate > Transient test failure >

[jira] [Resolved] (KAFKA-4835) Allow users control over repartitioning

[ https://issues.apache.org/jira/browse/KAFKA-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-4835. --- Resolution: Duplicate > Allow users control over repartitioning >

[jira] [Reopened] (KAFKA-4835) Allow users control over repartitioning

[ https://issues.apache.org/jira/browse/KAFKA-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reopened KAFKA-4835: --- > Allow users control over repartitioning > --- > >

[jira] [Commented] (KAFKA-5797) StoreChangelogReader should be resilient to broker-side metadata not available

[ https://issues.apache.org/jira/browse/KAFKA-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147481#comment-16147481 ] ASF GitHub Bot commented on KAFKA-5797: --- Github user asfgit closed the pull request at:

[jira] [Resolved] (KAFKA-5797) StoreChangelogReader should be resilient to broker-side metadata not available

[ https://issues.apache.org/jira/browse/KAFKA-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5797. -- Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3748

[jira] [Commented] (KAFKA-5649) Producer is being closed generating ssl exception

[ https://issues.apache.org/jira/browse/KAFKA-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147421#comment-16147421 ] Pablo Panero commented on KAFKA-5649: - [~nmanikumar] Will do, but will need time until I can relaunch

[jira] [Created] (KAFKA-5810) Improve authentication logging on the broker-side

Rajini Sivaram created KAFKA-5810: - Summary: Improve authentication logging on the broker-side Key: KAFKA-5810 URL: https://issues.apache.org/jira/browse/KAFKA-5810 Project: Kafka Issue

[jira] [Commented] (KAFKA-4905) StreamPartitionAssignor doesn't respect subscriptions to assign partitions.

[ https://issues.apache.org/jira/browse/KAFKA-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147193#comment-16147193 ] Fredrik Vraalsen commented on KAFKA-4905: - We figured out the solution: Just needed to scale down

[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 ] Romaric Parmentier updated KAFKA-5060: -- Labels: (was: reliability) > Offset not found while broker is rebuilding its index

[jira] [Commented] (KAFKA-5804) ChangeLoggingWindowBytesStore needs to retain duplicates when writing to the log

[ https://issues.apache.org/jira/browse/KAFKA-5804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147175#comment-16147175 ] ASF GitHub Bot commented on KAFKA-5804: --- Github user asfgit closed the pull request at:

[jira] [Resolved] (KAFKA-5804) ChangeLoggingWindowBytesStore needs to retain duplicates when writing to the log

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

[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=16147141#comment-16147141 ] Spiros Ioannou commented on KAFKA-5060: --- We get the same error on every restart on kafka 0.11:

[jira] [Commented] (KAFKA-3131) Inappropriate logging level for SSL Problem

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

[jira] [Updated] (KAFKA-5762) Refactor AdminClient to use LogContext

[ https://issues.apache.org/jira/browse/KAFKA-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5762: --- Fix Version/s: 1.0.0 > Refactor AdminClient to use LogContext >

[jira] [Resolved] (KAFKA-5762) Refactor AdminClient to use LogContext

[ https://issues.apache.org/jira/browse/KAFKA-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5762. Resolution: Fixed > Refactor AdminClient to use LogContext > --

[jira] [Commented] (KAFKA-3039) Temporary loss of leader resulted in log being completely truncated

[ https://issues.apache.org/jira/browse/KAFKA-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147070#comment-16147070 ] Ivan Babrou commented on KAFKA-3039: We also experienced this and out of 28 upgraded nodes in one rack

[jira] [Resolved] (KAFKA-4297) Cannot Stop Kafka with Shell Script

[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4297. -- Resolution: Duplicate Closing this as there is a latest PR for KAFKA-4931. > Cannot Stop Kafka with

[jira] [Assigned] (KAFKA-5313) Improve exception handling on coordinator interactions

[ https://issues.apache.org/jira/browse/KAFKA-5313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-5313: --- Assignee: (was: Eno Thereska) > Improve exception handling on coordinator interactions >

[jira] [Assigned] (KAFKA-5499) Double check how we handle exceptions when commits fail

[ https://issues.apache.org/jira/browse/KAFKA-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-5499: --- Assignee: (was: Eno Thereska) > Double check how we handle exceptions when commits fail

[jira] [Assigned] (KAFKA-5569) Document any changes from this task

[ https://issues.apache.org/jira/browse/KAFKA-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-5569: --- Assignee: (was: Eno Thereska) > Document any changes from this task >

[jira] [Assigned] (KAFKA-5301) Improve exception handling on consumer path

[ https://issues.apache.org/jira/browse/KAFKA-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-5301: --- Assignee: (was: Eno Thereska) > Improve exception handling on consumer path >

[jira] [Commented] (KAFKA-5499) Double check how we handle exceptions when commits fail

[ https://issues.apache.org/jira/browse/KAFKA-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146996#comment-16146996 ] ASF GitHub Bot commented on KAFKA-5499: --- Github user enothereska closed the pull request at:

[jira] [Assigned] (KAFKA-3514) Stream timestamp computation needs some further thoughts

[ https://issues.apache.org/jira/browse/KAFKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-3514: --- Assignee: (was: Eno Thereska) > Stream timestamp computation needs some further thoughts

[jira] [Commented] (KAFKA-4905) StreamPartitionAssignor doesn't respect subscriptions to assign partitions.

[ https://issues.apache.org/jira/browse/KAFKA-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146985#comment-16146985 ] Fredrik Vraalsen commented on KAFKA-4905: - Hi! We've just stumbled upon this exception in our

[jira] [Updated] (KAFKA-5809) when zookeeper set acl on path /. then kafka can't connect zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] heping updated KAFKA-5809: -- Description: hi,all when i set zookeeper acl on zookeeper path /. using setAcl /

[jira] [Comment Edited] (KAFKA-5786) Yet another exception is causing that streamming app is zombie

[ https://issues.apache.org/jira/browse/KAFKA-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146805#comment-16146805 ] Seweryn Habdank-Wojewodzki edited comment on KAFKA-5786 at 8/30/17 7:23 AM:

[jira] [Updated] (KAFKA-5786) Yet another exception is causing that streamming app is zombie

[ https://issues.apache.org/jira/browse/KAFKA-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated KAFKA-5786: -- Attachment: fatal-errors-by-rebalancing.zip Logs from different apps

[jira] [Commented] (KAFKA-5779) Single message may exploit application based on KStream

[ https://issues.apache.org/jira/browse/KAFKA-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146794#comment-16146794 ] Seweryn Habdank-Wojewodzki commented on KAFKA-5779: --- OK. I will wait for 1.0 release.

[jira] [Updated] (KAFKA-5809) when zookeeper set acl on path /. then kafka can't connect zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] heping updated KAFKA-5809: -- Affects Version/s: 0.10.1.0 Description: when i set zookeeper acl on zookeeper path /. using setAcl /

[jira] [Updated] (KAFKA-5809) when zookeeper set acl on path /. then kafka can't connect zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] heping updated KAFKA-5809: -- Description: when i set zookeeper acl on zookeeper path /. using setAcl /

[jira] [Updated] (KAFKA-5809) when zookeeper set acl on path /. then kafka can't connect zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] heping updated KAFKA-5809: -- Attachment: 20170830135831.png > when zookeeper set acl on path /. then kafka can't connect zookeeper >

[jira] [Updated] (KAFKA-5809) when zookeeper set acl on path /. then kafka can't connect zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] heping updated KAFKA-5809: -- Attachment: (was: QQ截图20170830135831.png) > when zookeeper set acl on path /. then kafka can't connect

[jira] [Created] (KAFKA-5809) when zookeeper set acl on path /. then kafka can't connect zookeeper

heping created KAFKA-5809: - Summary: when zookeeper set acl on path /. then kafka can't connect zookeeper Key: KAFKA-5809 URL: https://issues.apache.org/jira/browse/KAFKA-5809 Project: Kafka Issue