[jira] [Issue Comment Deleted] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HongLiang updated KAFKA-6326: - Comment: was deleted (was: [~liuweiwell]gao xiao ne?) > when broker is unavailable(such as broker's

[jira] [Updated] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HongLiang updated KAFKA-6326: - Attachment: (was: fast-recver-shutdownbroker.diff) > when broker is unavailable(such as broker's

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283158#comment-16283158 ] HongLiang edited comment on KAFKA-6326 at 12/8/17 7:32 AM: --- sorry, the version

[jira] [Commented] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283158#comment-16283158 ] HongLiang commented on KAFKA-6326: -- sorry, the version is 0.10.2.1 > when broker is unavailable(such as

[jira] [Commented] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283156#comment-16283156 ] huxihx commented on KAFKA-6326: --- Based on the screenshot, it seems to be 0.10.2.1 codebase. Did you run into

[jira] [Updated] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HongLiang updated KAFKA-6326: - Attachment: (was: _f7d1d2b4-39ae-4e02-8519-99bcba849668.png) > when broker is unavailable(such as

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283053#comment-16283053 ] HongLiang edited comment on KAFKA-6326 at 12/8/17 4:51 AM: --- [~huxi_2b]

[jira] [Commented] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283053#comment-16283053 ] HongLiang commented on KAFKA-6326: -- [~huxi_2b] zookeeper.session.timeout.ms is 120 sec. but the zk

[jira] [Updated] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HongLiang updated KAFKA-6326: - Attachment: _f7d1d2b4-39ae-4e02-8519-99bcba849668.png > when broker is unavailable(such as broker's

[jira] [Commented] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283028#comment-16283028 ] huxihx commented on KAFKA-6326: --- What's your `zookeeper.session.timeout.ms`? And I am also curious about

[jira] [Commented] (KAFKA-6323) punctuate with WALL_CLOCK_TIME triggered immediately

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

[jira] [Created] (KAFKA-6329) Load trust store as a resource

Allen Wang created KAFKA-6329: - Summary: Load trust store as a resource Key: KAFKA-6329 URL: https://issues.apache.org/jira/browse/KAFKA-6329 Project: Kafka Issue Type: Improvement

[jira] [Assigned] (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:all-tabpanel ] Matthias J. Sax reassigned KAFKA-6126: -- Assignee: Matthias J. Sax > Reduce rebalance time by not checking if created topics

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282953#comment-16282953 ] HongLiang edited comment on KAFKA-6326 at 12/8/17 2:57 AM: --- [~liuweiwell]gao

[jira] [Commented] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282953#comment-16282953 ] HongLiang commented on KAFKA-6326: -- [~liuweiwell]gao xiao ni? > when broker is unavailable(such as

[jira] [Commented] (KAFKA-6318) StreamsResetter should return non-zero return code on error

[ https://issues.apache.org/jira/browse/KAFKA-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282932#comment-16282932 ] siva santhalingam commented on KAFKA-6318: -- Hi [~mjsax] Can i assign this to myself. Also

[jira] [Commented] (KAFKA-4857) Replace StreamsKafkaClient with AdminClient in Kafka Streams

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

[jira] [Updated] (KAFKA-6328) Exclude node groups belonging to global stores in InternalTopologyBuilder#makeNodeGroups

[ https://issues.apache.org/jira/browse/KAFKA-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6328: --- Affects Version/s: 1.0.0 > Exclude node groups belonging to global stores in >

[jira] [Created] (KAFKA-6328) Exclude node groups belonging to global stores in InternalTopologyBuilder#makeNodeGroups

Guozhang Wang created KAFKA-6328: Summary: Exclude node groups belonging to global stores in InternalTopologyBuilder#makeNodeGroups Key: KAFKA-6328 URL: https://issues.apache.org/jira/browse/KAFKA-6328

[jira] [Commented] (KAFKA-6327) IllegalArgumentException in RocksDB when RocksDBException being generated

[ https://issues.apache.org/jira/browse/KAFKA-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282593#comment-16282593 ] Matthias J. Sax commented on KAFKA-6327: Thanks for the heads up [~nyokodo]! >

[jira] [Commented] (KAFKA-6319) kafka-acls regression for comma characters (and maybe other characters as well)

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

[jira] [Created] (KAFKA-6327) IllegalArgumentException in RocksDB when RocksDBException being generated

Anthony May created KAFKA-6327: -- Summary: IllegalArgumentException in RocksDB when RocksDBException being generated Key: KAFKA-6327 URL: https://issues.apache.org/jira/browse/KAFKA-6327 Project: Kafka

[jira] [Updated] (KAFKA-6323) punctuate with WALL_CLOCK_TIME triggered immediately

[ https://issues.apache.org/jira/browse/KAFKA-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6323: --- Fix Version/s: 1.1.0 > punctuate with WALL_CLOCK_TIME triggered immediately >

[jira] [Commented] (KAFKA-6260) AbstractCoordinator not clearly handles NULL Exception

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282274#comment-16282274 ] Matthias J. Sax commented on KAFKA-6260: You could check out

[jira] [Commented] (KAFKA-6322) Error deleting log for topic, all log dirs failed.

[ https://issues.apache.org/jira/browse/KAFKA-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282200#comment-16282200 ] Ismael Juma commented on KAFKA-6322: The issue was always related to holding a file handle while

[jira] [Commented] (KAFKA-6322) Error deleting log for topic, all log dirs failed.

[ https://issues.apache.org/jira/browse/KAFKA-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282186#comment-16282186 ] Ted Yu commented on KAFKA-6322: --- Edited previous comment. Since Dongyan's case was not for file not existing

[jira] [Comment Edited] (KAFKA-6322) Error deleting log for topic, all log dirs failed.

[ https://issues.apache.org/jira/browse/KAFKA-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282120#comment-16282120 ] Ted Yu edited comment on KAFKA-6322 at 12/7/17 5:20 PM: FileSystemException was

[jira] [Commented] (KAFKA-6322) Error deleting log for topic, all log dirs failed.

[ https://issues.apache.org/jira/browse/KAFKA-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282156#comment-16282156 ] Ismael Juma commented on KAFKA-6322: It was thrown by Files.delete as shown by the stacktrace. Not

[jira] [Commented] (KAFKA-6322) Error deleting log for topic, all log dirs failed.

[ https://issues.apache.org/jira/browse/KAFKA-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282120#comment-16282120 ] Ted Yu commented on KAFKA-6322: --- FileSystemException was encountered in Dongyan's case (which is not among

[jira] [Commented] (KAFKA-6199) Single broker with fast growing heap usage

[ https://issues.apache.org/jira/browse/KAFKA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282116#comment-16282116 ] Manikumar commented on KAFKA-6199: -- [~rt_skyscanner] yes, jstack output > Single broker with fast

[jira] [Commented] (KAFKA-6199) Single broker with fast growing heap usage

[ https://issues.apache.org/jira/browse/KAFKA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282111#comment-16282111 ] Robin Tweedie commented on KAFKA-6199: -- [~omkreddy] Nothing obvious beyond the warnings I shared

[jira] [Commented] (KAFKA-6324) Change LogSegment.delete to deleteIfExists and harden log recovery

[ https://issues.apache.org/jira/browse/KAFKA-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282109#comment-16282109 ] Ismael Juma commented on KAFKA-6324: https://github.com/apache/kafka/pull/4040 > Change

[jira] [Updated] (KAFKA-6324) Change LogSegment.delete to deleteIfExists and harden log recovery

[ https://issues.apache.org/jira/browse/KAFKA-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6324: --- Description: Fixes KAFKA-6194 and a delete while open issue (KAFKA-6322 and KAFKA-6075) and makes the

[jira] [Commented] (KAFKA-6322) Error deleting log for topic, all log dirs failed.

[ https://issues.apache.org/jira/browse/KAFKA-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282105#comment-16282105 ] Ismael Juma commented on KAFKA-6322: Probably a duplicate of KAFKA-6324, that is nearly ready to be

[jira] [Commented] (KAFKA-6322) Error deleting log for topic, all log dirs failed.

[ https://issues.apache.org/jira/browse/KAFKA-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282064#comment-16282064 ] dongyan li commented on KAFKA-6322: --- Yes, I think they attribute to the same problem. However, instead

[jira] [Commented] (KAFKA-6199) Single broker with fast growing heap usage

[ https://issues.apache.org/jira/browse/KAFKA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282041#comment-16282041 ] Manikumar commented on KAFKA-6199: -- Are there any exceptions in the broker? Can you upload the thread

[jira] [Commented] (KAFKA-6325) Producer.flush() doesn't throw exception on timeout

[ https://issues.apache.org/jira/browse/KAFKA-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282030#comment-16282030 ] Ted Yu commented on KAFKA-6325: --- I assume you have modified your producer code to accommodate this behavior.

[jira] [Issue Comment Deleted] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wei liu updated KAFKA-6326: --- Comment: was deleted (was: Hi [~China body] {panel:title=My SQL

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281987#comment-16281987 ] wei liu edited comment on KAFKA-6326 at 12/7/17 3:19 PM: - Hi [~China body]

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281987#comment-16281987 ] wei liu edited comment on KAFKA-6326 at 12/7/17 3:18 PM: - {panel:title=My SQL

[jira] [Commented] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281987#comment-16281987 ] wei liu commented on KAFKA-6326: {panel:title=My SQL

[jira] [Created] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

HongLiang created KAFKA-6326: Summary: when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout Key: KAFKA-6326 URL: https://issues.apache.org/jira/browse/KAFKA-6326

[jira] [Created] (KAFKA-6325) Producer.flush() doesn't throw exception on timeout

Erik Scheuter created KAFKA-6325: Summary: Producer.flush() doesn't throw exception on timeout Key: KAFKA-6325 URL: https://issues.apache.org/jira/browse/KAFKA-6325 Project: Kafka Issue

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

[ https://issues.apache.org/jira/browse/KAFKA-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281779#comment-16281779 ] Sergey AKhmatov commented on KAFKA-3240: Happens to me as well. kafka 1.0.0 3-node setup on

[jira] [Commented] (KAFKA-1996) Scaladoc error: unknown tag parameter

[ https://issues.apache.org/jira/browse/KAFKA-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281760#comment-16281760 ] Andy Doddington commented on KAFKA-1996: I am getting this error on scala docs that I have added

[jira] [Assigned] (KAFKA-5272) Improve validation for Alter Configs (KIP-133)

[ https://issues.apache.org/jira/browse/KAFKA-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5272: -- Assignee: (was: Ismael Juma) > Improve validation for Alter Configs (KIP-133) >

[jira] [Assigned] (KAFKA-5276) Support derived and prefixed configs in DescribeConfigs (KIP-133)

[ https://issues.apache.org/jira/browse/KAFKA-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5276: -- Assignee: (was: Ismael Juma) > Support derived and prefixed configs in DescribeConfigs

[jira] [Assigned] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3665: -- Assignee: (was: Ismael Juma) > Default ssl.endpoint.identification.algorithm should be

[jira] [Assigned] (KAFKA-4680) min.insync.replicas can be set higher than replication factor

[ https://issues.apache.org/jira/browse/KAFKA-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4680: -- Assignee: (was: Ismael Juma) > min.insync.replicas can be set higher than replication

[jira] [Assigned] (KAFKA-4637) Update system test(s) to use multiple listeners for the same security protocol

[ https://issues.apache.org/jira/browse/KAFKA-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4637: -- Assignee: (was: Ismael Juma) > Update system test(s) to use multiple listeners for the

[jira] [Assigned] (KAFKA-6319) kafka-acls regression for comma characters (and maybe other characters as well)

[ https://issues.apache.org/jira/browse/KAFKA-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-6319: - Assignee: Rajini Sivaram > kafka-acls regression for comma characters (and maybe other

[jira] [Resolved] (KAFKA-6313) Kafka Core should have explicit SLF4J API dependency

[ https://issues.apache.org/jira/browse/KAFKA-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6313. Resolution: Fixed > Kafka Core should have explicit SLF4J API dependency >

[jira] [Updated] (KAFKA-6313) Kafka Core should have explicit SLF4J API dependency

[ https://issues.apache.org/jira/browse/KAFKA-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6313: --- Description: In an application that depends on the Kafka server artifacts with: {code:xml}

[jira] [Updated] (KAFKA-6313) Kafka Core should have explicit SLF4J API dependency

[ https://issues.apache.org/jira/browse/KAFKA-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6313: --- Summary: Kafka Core should have explicit SLF4J API dependency (was: Kafka Core maven dependencies

[jira] [Commented] (KAFKA-6313) Kafka Core maven dependencies are missing SLF4J API

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

[jira] [Commented] (KAFKA-6323) punctuate with WALL_CLOCK_TIME triggered immediately

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

[jira] [Commented] (KAFKA-5882) NullPointerException in StreamTask

[ https://issues.apache.org/jira/browse/KAFKA-5882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281484#comment-16281484 ] Seweryn Habdank-Wojewodzki commented on KAFKA-5882: --- Hmm... I will try to retest all

[jira] [Comment Edited] (KAFKA-5882) NullPointerException in StreamTask

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

[jira] [Commented] (KAFKA-6260) AbstractCoordinator not clearly handles NULL Exception

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281481#comment-16281481 ] Seweryn Habdank-Wojewodzki commented on KAFKA-6260: --- Thanks a lot! When releases will