[jira] [Updated] (KAFKA-6481) Improving performance of the function ControllerChannelManager.addUpdateMetadataRequestForBrokers

[ https://issues.apache.org/jira/browse/KAFKA-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Wang updated KAFKA-6481: -- Description: The function ControllerChannelManager.addUpdateMetadataRequestForBrokers should only proce

[jira] [Updated] (KAFKA-6481) Improving performance of the function ControllerChannelManager.addUpdateMetadataRequestForBrokers

[ https://issues.apache.org/jira/browse/KAFKA-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Wang updated KAFKA-6481: -- Description: The function ControllerChannelManager.addUpdateMetadataRequestForBrokers should only proce

[jira] [Commented] (KAFKA-6541) StackOverflow exceptions in thread 'kafka-coordinator-heartbeat-thread

[ https://issues.apache.org/jira/browse/KAFKA-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356756#comment-16356756 ] huxihx commented on KAFKA-6541: --- Seems `coordinatorDead` was recursively called  which could

[jira] [Updated] (KAFKA-6541) StackOverflow exceptions in thread 'kafka-coordinator-heartbeat-thread

[ https://issues.apache.org/jira/browse/KAFKA-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anh Le updated KAFKA-6541: -- Description: There's something wrong with our client library when sending heart beats. This bug seems to be ide

[jira] [Commented] (KAFKA-6541) StackOverflow exceptions in thread 'kafka-coordinator-heartbeat-thread

[ https://issues.apache.org/jira/browse/KAFKA-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356818#comment-16356818 ] ASF GitHub Bot commented on KAFKA-6541: --- anhldbk opened a new pull request #4548: KA

[jira] [Commented] (KAFKA-6541) StackOverflow exceptions in thread 'kafka-coordinator-heartbeat-thread

[ https://issues.apache.org/jira/browse/KAFKA-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356819#comment-16356819 ] Anh Le commented on KAFKA-6541: --- [~huxi_2b] I created [a PR|https://github.com/apache/kafka/

[jira] [Commented] (KAFKA-6424) QueryableStateIntegrationTest#queryOnRebalance should accept raw text

[ https://issues.apache.org/jira/browse/KAFKA-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356836#comment-16356836 ] Filipe Agapito commented on KAFKA-6424: --- This happens because {{createCountStream}}

[jira] [Commented] (KAFKA-6424) QueryableStateIntegrationTest#queryOnRebalance should accept raw text

[ https://issues.apache.org/jira/browse/KAFKA-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356842#comment-16356842 ] ASF GitHub Bot commented on KAFKA-6424: --- h314to opened a new pull request #4549: KAF

[jira] [Commented] (KAFKA-5165) Kafka Logs Cleanup Not happening, Huge File Growth - Windows

[ https://issues.apache.org/jira/browse/KAFKA-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356937#comment-16356937 ] Akash C commented on KAFKA-5165: We are facing a similar issue in 0.11.0.0. Is there a wor

[jira] [Created] (KAFKA-6542) Tables should trigger joins too, not just streams

Antony Stubbs created KAFKA-6542: Summary: Tables should trigger joins too, not just streams Key: KAFKA-6542 URL: https://issues.apache.org/jira/browse/KAFKA-6542 Project: Kafka Issue Type: I

[jira] [Created] (KAFKA-6543) Allow KTables to be bootstrapped at start up, like GKTables

Antony Stubbs created KAFKA-6543: Summary: Allow KTables to be bootstrapped at start up, like GKTables Key: KAFKA-6543 URL: https://issues.apache.org/jira/browse/KAFKA-6543 Project: Kafka Is

[jira] [Updated] (KAFKA-6543) Allow KTables to be bootstrapped at start up, like GKTables

[ https://issues.apache.org/jira/browse/KAFKA-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antony Stubbs updated KAFKA-6543: - Affects Version/s: 1.1.0 Description: In some uses cases, it's desirable to have KTables

[jira] [Updated] (KAFKA-6542) Tables should trigger joins too, not just streams

[ https://issues.apache.org/jira/browse/KAFKA-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antony Stubbs updated KAFKA-6542: - Description: At the moment it's quite possible to have a race condition when joining a stream wit

[jira] [Commented] (KAFKA-6543) Allow KTables to be bootstrapped at start up, like GKTables

[ https://issues.apache.org/jira/browse/KAFKA-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356975#comment-16356975 ] Antony Stubbs commented on KAFKA-6543: -- Close - duplicate of KAFKA-4113 Allow KTable

[jira] [Updated] (KAFKA-6542) Tables should trigger joins too, not just streams

[ https://issues.apache.org/jira/browse/KAFKA-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antony Stubbs updated KAFKA-6542: - Description: At the moment it's quite possible to have a race condition when joining a stream wit

[jira] [Updated] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3177: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Kafka consumer can hang when position() is ca

[jira] [Updated] (KAFKA-3438) Rack Aware Replica Reassignment should warn of overloaded brokers

[ https://issues.apache.org/jira/browse/KAFKA-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3438: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Rack Aware Replica Reassignment should warn o

[jira] [Updated] (KAFKA-3190) KafkaProducer should not invoke callback in send()

[ https://issues.apache.org/jira/browse/KAFKA-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3190: -- Fix Version/s: (was: 1.1.0) 2.0.0 > KafkaProducer should not invoke callback in s

[jira] [Updated] (KAFKA-3554) Generate actual data with specific compression ratio and add multi-thread support in the ProducerPerformance tool.

[ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3554: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Generate actual data with specific compressio

[jira] [Updated] (KAFKA-3689) Exception when attempting to decrease connection count for address with no connections

[ https://issues.apache.org/jira/browse/KAFKA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3689: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Exception when attempting to decrease connect

[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 ] Damian Guy updated KAFKA-4203: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Java producer default max message size does n

[jira] [Updated] (KAFKA-4249) Document how to customize GC logging options for broker

[ https://issues.apache.org/jira/browse/KAFKA-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4249: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Document how to customize GC logging options

[jira] [Updated] (KAFKA-4862) Kafka client connect to a shutdown node will block for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4862: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Kafka client connect to a shutdown node will

[jira] [Updated] (KAFKA-4665) Inconsistent handling of non-existing topics in offset fetch handling

[ https://issues.apache.org/jira/browse/KAFKA-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4665: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Inconsistent handling of non-existing topics

[jira] [Updated] (KAFKA-4307) Inconsistent parameters between console producer and consumer

[ https://issues.apache.org/jira/browse/KAFKA-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4307: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Inconsistent parameters between console produ

[jira] [Commented] (KAFKA-4879) KafkaConsumer.position may hang forever when deleting a topic

[ https://issues.apache.org/jira/browse/KAFKA-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356998#comment-16356998 ] Damian Guy commented on KAFKA-4879: --- [~hachikuji] is this going to make it for 1.1? > K

[jira] [Updated] (KAFKA-3297) More optimally balanced partition assignment strategy (new consumer)

[ https://issues.apache.org/jira/browse/KAFKA-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3297: -- Fix Version/s: (was: 1.1.0) 2.0.0 > More optimally balanced partition assignment

[jira] [Updated] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-2435: -- Fix Version/s: (was: 1.1.0) 2.0.0 > More optimally balanced partition assignment

[jira] [Updated] (KAFKA-4914) Partition re-assignment tool should check types before persisting state in ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4914: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Partition re-assignment tool should check typ

[jira] [Updated] (KAFKA-5029) cleanup javadocs and logging

[ https://issues.apache.org/jira/browse/KAFKA-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5029: -- Fix Version/s: (was: 1.1.0) 2.0.0 > cleanup javadocs and logging > --

[jira] [Updated] (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 ] Damian Guy updated KAFKA-5272: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Improve validation for Alter Configs (KIP-133

[jira] [Updated] (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 ] Damian Guy updated KAFKA-5276: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Support derived and prefixed configs in Descr

[jira] [Updated] (KAFKA-4701) Allow kafka brokers to dynamically reload truststore without restarting.

[ https://issues.apache.org/jira/browse/KAFKA-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4701: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Allow kafka brokers to dynamically reload tru

[jira] [Updated] (KAFKA-5403) Transactions system test should dedup consumed messages by offset

[ https://issues.apache.org/jira/browse/KAFKA-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5403: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Transactions system test should dedup consume

[jira] [Updated] (KAFKA-5445) Document exceptions thrown by AdminClient methods

[ https://issues.apache.org/jira/browse/KAFKA-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5445: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Document exceptions thrown by AdminClient met

[jira] [Updated] (KAFKA-5637) Document compatibility and release policies

[ https://issues.apache.org/jira/browse/KAFKA-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5637: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Document compatibility and release policies >

[jira] [Updated] (KAFKA-5944) Add unit tests for handling of authentication failures in clients

[ https://issues.apache.org/jira/browse/KAFKA-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5944: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Add unit tests for handling of authentication

[jira] [Updated] (KAFKA-5886) Introduce delivery.timeout.ms producer config (KIP-91)

[ https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5886: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Introduce delivery.timeout.ms producer config

[jira] [Updated] (KAFKA-5951) Autogenerate Producer RecordAccumulator metrics

[ https://issues.apache.org/jira/browse/KAFKA-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5951: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Autogenerate Producer RecordAccumulator metri

[jira] [Updated] (KAFKA-6390) Update ZooKeeper to 3.4.11, Gradle and other minor updates

[ https://issues.apache.org/jira/browse/KAFKA-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-6390: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Update ZooKeeper to 3.4.11, Gradle and other

[jira] [Updated] (KAFKA-5952) Refactor Consumer Fetcher metrics

[ https://issues.apache.org/jira/browse/KAFKA-5952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5952: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Refactor Consumer Fetcher metrics > -

[jira] [Updated] (KAFKA-5914) Return MessageFormatVersion and MessageMaxBytes in MetadataResponse

[ https://issues.apache.org/jira/browse/KAFKA-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5914: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Return MessageFormatVersion and MessageMaxByt

[jira] [Updated] (KAFKA-3575) Use console consumer access topic that does not exist, can not use "Control + C" to exit process

[ https://issues.apache.org/jira/browse/KAFKA-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3575: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Use console consumer access topic that does n

[jira] [Updated] (KAFKA-3733) Avoid long command lines by setting CLASSPATH in environment

[ https://issues.apache.org/jira/browse/KAFKA-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3733: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Avoid long command lines by setting CLASSPATH

[jira] [Updated] (KAFKA-3999) Consumer bytes-fetched metric uses decompressed message size

[ https://issues.apache.org/jira/browse/KAFKA-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3999: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Consumer bytes-fetched metric uses decompress

[jira] [Updated] (KAFKA-4931) stop script fails due 4096 ps output limit

[ https://issues.apache.org/jira/browse/KAFKA-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4931: -- Fix Version/s: (was: 1.1.0) 2.0.0 > stop script fails due 4096 ps output limit >

[jira] [Updated] (KAFKA-4126) No relevant log when the topic is non-existent

[ https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4126: -- Fix Version/s: (was: 1.1.0) 2.0.0 > No relevant log when the topic is non-existen

[jira] [Updated] (KAFKA-4893) async topic deletion conflicts with max topic length

[ https://issues.apache.org/jira/browse/KAFKA-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4893: -- Fix Version/s: (was: 1.1.0) 2.0.0 > async topic deletion conflicts with max topic

[jira] [Updated] (KAFKA-4794) Add access to OffsetStorageReader from SourceConnector

[ https://issues.apache.org/jira/browse/KAFKA-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4794: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Add access to OffsetStorageReader from Source

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

[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4950: -- Fix Version/s: (was: 1.1.0) 2.0.0 > ConcurrentModificationException when iteratin

[jira] [Updated] (KAFKA-5359) Exceptions from RequestFuture lack parts of the stack trace

[ https://issues.apache.org/jira/browse/KAFKA-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5359: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Exceptions from RequestFuture lack parts of t

[jira] [Updated] (KAFKA-5692) Refactor PreferredReplicaLeaderElectionCommand to use AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5692: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Refactor PreferredReplicaLeaderElectionComman

[jira] [Updated] (KAFKA-5479) Docs for authorization omit authorizer.class.name

[ https://issues.apache.org/jira/browse/KAFKA-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5479: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Docs for authorization omit authorizer.class.

[jira] [Updated] (KAFKA-5517) Support linking to particular configuration parameters

[ https://issues.apache.org/jira/browse/KAFKA-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5517: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Support linking to particular configuration p

[jira] [Updated] (KAFKA-5532) Making bootstrap.servers property a first citizen option for the ProducerPerformance

[ https://issues.apache.org/jira/browse/KAFKA-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5532: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Making bootstrap.servers property a first cit

[jira] [Updated] (KAFKA-5919) Adding checks on "version" field for tools using it

[ https://issues.apache.org/jira/browse/KAFKA-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5919: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Adding checks on "version" field for tools us

[jira] [Updated] (KAFKA-6448) Mx4jLoader#props.getBoolean("kafka_mx4jenable", false) conflict with the annotation

[ https://issues.apache.org/jira/browse/KAFKA-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-6448: -- Fix Version/s: (was: 1.1.0) 2.0.0 > Mx4jLoader#props.getBoolean("kafka_mx4jenable

[jira] [Commented] (KAFKA-6529) Broker leaks memory and file descriptors after sudden client disconnects

[ https://issues.apache.org/jira/browse/KAFKA-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357015#comment-16357015 ] Damian Guy commented on KAFKA-6529: --- [~ijuma] should this go in to 1.1? > Broker leaks

[jira] [Updated] (KAFKA-6481) Improving performance of the function ControllerChannelManager.addUpdateMetadataRequestForBrokers

[ https://issues.apache.org/jira/browse/KAFKA-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Wang updated KAFKA-6481: -- Description: The function ControllerChannelManager.addUpdateMetadataRequestForBrokers should only proce

[jira] [Resolved] (KAFKA-6504) Connect: Some per-task-metrics not working

[ https://issues.apache.org/jira/browse/KAFKA-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6504. Resolution: Fixed Fix Version/s: 1.1.0 > Connect: Some per-task-metrics not working >

[jira] [Commented] (KAFKA-6517) ZooKeeperClient holds a lock while waiting for responses, blocking shutdown

[ https://issues.apache.org/jira/browse/KAFKA-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357199#comment-16357199 ] ASF GitHub Bot commented on KAFKA-6517: --- rajinisivaram opened a new pull request #45

[jira] [Commented] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357203#comment-16357203 ] Jeff Widman commented on KAFKA-2435: Can this be closed as wontfix?  Two reasons:  

[jira] [Comment Edited] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357203#comment-16357203 ] Jeff Widman edited comment on KAFKA-2435 at 2/8/18 4:51 PM: Ca

[jira] [Comment Edited] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357203#comment-16357203 ] Jeff Widman edited comment on KAFKA-2435 at 2/8/18 4:51 PM: Ca

[jira] [Comment Edited] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357203#comment-16357203 ] Jeff Widman edited comment on KAFKA-2435 at 2/8/18 4:54 PM: Ca

[jira] [Commented] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357214#comment-16357214 ] Andrew Olson commented on KAFKA-2435: - [~jeffwidman] yes, that sounds quite reasonable

[jira] [Commented] (KAFKA-4914) Partition re-assignment tool should check types before persisting state in ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357221#comment-16357221 ] Nick Travers commented on KAFKA-4914: - [~damianguy] - noticed this got updated recentl

[jira] [Resolved] (KAFKA-6543) Allow KTables to be bootstrapped at start up, like GKTables

[ https://issues.apache.org/jira/browse/KAFKA-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6543. Resolution: Duplicate > Allow KTables to be bootstrapped at start up, like GKTables > --

[jira] [Commented] (KAFKA-6541) StackOverflow exceptions in thread 'kafka-coordinator-heartbeat-thread

[ https://issues.apache.org/jira/browse/KAFKA-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357279#comment-16357279 ] Jason Gustafson commented on KAFKA-6541: [~anhldbk] This was fixed in KAFKA-6366 w

[jira] [Commented] (KAFKA-6362) auto commit not work since coordinatorUnknown() is always true.

[ https://issues.apache.org/jira/browse/KAFKA-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357298#comment-16357298 ] ASF GitHub Bot commented on KAFKA-6362: --- hachikuji closed pull request #4326: KAFKA-

[jira] [Updated] (KAFKA-6362) auto commit not work since coordinatorUnknown() is always true.

[ https://issues.apache.org/jira/browse/KAFKA-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-6362: --- Component/s: consumer > auto commit not work since coordinatorUnknown() is always true. >

[jira] [Resolved] (KAFKA-6362) auto commit not work since coordinatorUnknown() is always true.

[ https://issues.apache.org/jira/browse/KAFKA-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6362. Resolution: Fixed Fix Version/s: 1.1.0 > auto commit not work since coordinatorUnknow

[jira] [Commented] (KAFKA-6388) Error while trying to roll a segment that already exists

[ https://issues.apache.org/jira/browse/KAFKA-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357331#comment-16357331 ] Paul Davidson commented on KAFKA-6388: -- [~dhay]  We saw this on non-compacted topics.

[jira] [Commented] (KAFKA-6388) Error while trying to roll a segment that already exists

[ https://issues.apache.org/jira/browse/KAFKA-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357401#comment-16357401 ] Graham Campbell commented on KAFKA-6388: Most of the recent times we've run into t

[jira] [Created] (KAFKA-6544) kafka process should exit when it encounters "java.io.IOException: Too many open files"

Yu Yang created KAFKA-6544: -- Summary: kafka process should exit when it encounters "java.io.IOException: Too many open files" Key: KAFKA-6544 URL: https://issues.apache.org/jira/browse/KAFKA-6544 Project:

[jira] [Commented] (KAFKA-6544) kafka process should exit when it encounters "java.io.IOException: Too many open files"

[ https://issues.apache.org/jira/browse/KAFKA-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357419#comment-16357419 ] Ted Yu commented on KAFKA-6544: --- One option is to shutdown the process in SocketServer : {co

[jira] [Commented] (KAFKA-6544) kafka process should exit when it encounters "java.io.IOException: Too many open files"

[ https://issues.apache.org/jira/browse/KAFKA-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357456#comment-16357456 ] Colin P. McCabe commented on KAFKA-6544: What are the open file descriptors that y

[jira] [Assigned] (KAFKA-6345) NetworkClient.inFlightRequestCount() is not thread safe, causing ConcurrentModificationExceptions when sensors are read

[ https://issues.apache.org/jira/browse/KAFKA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] radai rosenblatt reassigned KAFKA-6345: --- Assignee: Sean McCauliff > NetworkClient.inFlightRequestCount() is not thread safe, c

[jira] [Resolved] (KAFKA-6345) NetworkClient.inFlightRequestCount() is not thread safe, causing ConcurrentModificationExceptions when sensors are read

[ https://issues.apache.org/jira/browse/KAFKA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] radai rosenblatt resolved KAFKA-6345. - Resolution: Fixed > NetworkClient.inFlightRequestCount() is not thread safe, causing > Co

[jira] [Updated] (KAFKA-6345) NetworkClient.inFlightRequestCount() is not thread safe, causing ConcurrentModificationExceptions when sensors are read

[ https://issues.apache.org/jira/browse/KAFKA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] radai rosenblatt updated KAFKA-6345: Fix Version/s: 1.1.0 > NetworkClient.inFlightRequestCount() is not thread safe, causing > C

[jira] [Commented] (KAFKA-6544) kafka process should exit when it encounters "java.io.IOException: Too many open files"

[ https://issues.apache.org/jira/browse/KAFKA-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357483#comment-16357483 ] Yu Yang commented on KAFKA-6544: [~cmccabe] The kafka process is in `` status. sudo ls -

[jira] [Updated] (KAFKA-6390) Update ZooKeeper to 3.4.11, Gradle and other minor updates

[ https://issues.apache.org/jira/browse/KAFKA-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6390: --- Fix Version/s: (was: 2.0.0) 1.1.0 > Update ZooKeeper to 3.4.11, Gradle and othe

[jira] [Updated] (KAFKA-6544) kafka process should exit when it encounters "java.io.IOException: Too many open files"

[ https://issues.apache.org/jira/browse/KAFKA-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Yang updated KAFKA-6544: --- Description: Our kafka cluster encountered a few disk/xfs failures in the cloud vm instances. When a disk/xfs

[jira] [Created] (KAFKA-6545) AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0

Chong Wang created KAFKA-6545: - Summary: AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0 Key: KAFKA-6545 URL: https://issues.apache.org/jira/browse/KAFKA-6545 Project: Kafka Issue

[jira] [Updated] (KAFKA-6545) AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chong Wang updated KAFKA-6545: -- Description: Not sure why this function is deleted ([https://github.com/apache/kafka/commit/1d24e10aeab

[jira] [Commented] (KAFKA-6545) AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357577#comment-16357577 ] Ismael Juma commented on KAFKA-6545: The commit description states why they were remov

[jira] [Commented] (KAFKA-6388) Error while trying to roll a segment that already exists

[ https://issues.apache.org/jira/browse/KAFKA-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357588#comment-16357588 ] David Hay commented on KAFKA-6388: -- I'm pretty sure we're not using compacted topics.  It

[jira] [Updated] (KAFKA-6538) Enhance ByteStore exceptions with more context information

[ https://issues.apache.org/jira/browse/KAFKA-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6538: --- Affects Version/s: (was: 1.2.0) 1.1.0 > Enhance ByteStore exception

[jira] [Commented] (KAFKA-3625) Move kafka-streams test fixtures into a published package

[ https://issues.apache.org/jira/browse/KAFKA-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357609#comment-16357609 ] ASF GitHub Bot commented on KAFKA-3625: --- mjsax closed pull request #4493: KAFKA-3625

[jira] [Commented] (KAFKA-6545) AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357615#comment-16357615 ] Chong Wang commented on KAFKA-6545: --- [~ijuma] Thanks, I was thinking it's AdminClient.sc

[jira] [Resolved] (KAFKA-6545) AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chong Wang resolved KAFKA-6545. --- Resolution: Not A Problem > AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0 > --

[jira] [Commented] (KAFKA-6529) Broker leaks memory and file descriptors after sudden client disconnects

[ https://issues.apache.org/jira/browse/KAFKA-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357626#comment-16357626 ] Ismael Juma commented on KAFKA-6529: [~damianguy] Yes, I think the PR should be merged

[jira] [Created] (KAFKA-6546) Add ENDPOINT_NOT_FOUND_ON_LEADER error code for missing listener

Rajini Sivaram created KAFKA-6546: - Summary: Add ENDPOINT_NOT_FOUND_ON_LEADER error code for missing listener Key: KAFKA-6546 URL: https://issues.apache.org/jira/browse/KAFKA-6546 Project: Kafka

[jira] [Created] (KAFKA-6547) group offset reset and begin_offset ignored/no effect

Dan created KAFKA-6547: -- Summary: group offset reset and begin_offset ignored/no effect Key: KAFKA-6547 URL: https://issues.apache.org/jira/browse/KAFKA-6547 Project: Kafka Issue Type: Bug Com

[jira] [Created] (KAFKA-6548) Migrate committed offsets from ZooKeeper to Kafka

Manikandan P created KAFKA-6548: --- Summary: Migrate committed offsets from ZooKeeper to Kafka Key: KAFKA-6548 URL: https://issues.apache.org/jira/browse/KAFKA-6548 Project: Kafka Issue Type: Imp

[jira] [Comment Edited] (KAFKA-6388) Error while trying to roll a segment that already exists

[ https://issues.apache.org/jira/browse/KAFKA-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357331#comment-16357331 ] Paul Davidson edited comment on KAFKA-6388 at 2/9/18 12:03 AM: -

[jira] [Commented] (KAFKA-6208) Reduce startup time for Kafka Connect workers

[ https://issues.apache.org/jira/browse/KAFKA-6208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357745#comment-16357745 ] Satyajit varma commented on KAFKA-6208: --- [~rhauch] , we could make the connectors,SM

[jira] [Commented] (KAFKA-6501) Add test to verify markPartitionsForTruncation after fetcher thread pool resize

[ https://issues.apache.org/jira/browse/KAFKA-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357749#comment-16357749 ] ASF GitHub Bot commented on KAFKA-6501: --- hachikuji closed pull request #4539: KAFKA-

[jira] [Resolved] (KAFKA-6501) Add test to verify markPartitionsForTruncation after fetcher thread pool resize

[ https://issues.apache.org/jira/browse/KAFKA-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6501. Resolution: Fixed Fix Version/s: (was: 1.2.0) 1.1.0 > Add test

[jira] [Commented] (KAFKA-2967) Move Kafka documentation to ReStructuredText

[ https://issues.apache.org/jira/browse/KAFKA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357798#comment-16357798 ] Vik Gamov commented on KAFKA-2967: -- Guys, Have we ever consider to use asciidoc [http:/

  1   2   >