[jira] [Commented] (KAFKA-4169) Calculation of message size is too conservative for compressed messages

[ https://issues.apache.org/jira/browse/KAFKA-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159621#comment-16159621 ] Joel Koshy commented on KAFKA-4169: --- I had been meaning to comment on this a while back but did not get

[jira] [Commented] (KAFKA-5505) Connect: Do not restart connector and existing tasks on task-set change

[ https://issues.apache.org/jira/browse/KAFKA-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159614#comment-16159614 ] Ted Yu commented on KAFKA-5505: --- bq. source-connector out-of-the-box that can copy from a relational

[jira] [Created] (KAFKA-5865) Expiring batches with idempotence enabled could cause data loss.

Apurva Mehta created KAFKA-5865: --- Summary: Expiring batches with idempotence enabled could cause data loss. Key: KAFKA-5865 URL: https://issues.apache.org/jira/browse/KAFKA-5865 Project: Kafka

[jira] [Commented] (KAFKA-5845) KafkaController should send LeaderAndIsrRequest to broker which starts very soon after shutdown

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

[jira] [Resolved] (KAFKA-5845) KafkaController should send LeaderAndIsrRequest to broker which starts very soon after shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-5845. - Resolution: Won't Fix > KafkaController should send LeaderAndIsrRequest to broker which starts very >

[jira] [Updated] (KAFKA-5864) ReplicaFetcherThread should not die if there is offline log directory

[ https://issues.apache.org/jira/browse/KAFKA-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-5864: Summary: ReplicaFetcherThread should not die if there is offline log directory (was:

[jira] [Updated] (KAFKA-5864) ReplicaFetcherThread should not die due to replica in offline log directory

[ https://issues.apache.org/jira/browse/KAFKA-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-5864: Summary: ReplicaFetcherThread should not die due to replica in offline log directory (was:

[jira] [Commented] (KAFKA-5792) Transient failure in KafkaAdminClientTest.testHandleTimeout

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

[jira] [Commented] (KAFKA-5696) SourceConnector does not commit offset on rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159476#comment-16159476 ] Randall Hauch commented on KAFKA-5696: -- No, it's not a straightforward change to only rebalance the

[jira] [Comment Edited] (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=16159461#comment-16159461 ] Randall Hauch edited comment on KAFKA-4107 at 9/8/17 10:32 PM: --- Not sure if

[jira] [Commented] (KAFKA-5825) Streams not processing when exactly once is set

[ https://issues.apache.org/jira/browse/KAFKA-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159375#comment-16159375 ] Guozhang Wang commented on KAFKA-5825: -- I tried to re-run your test code but with no luck to compile.

[jira] [Created] (KAFKA-5864) ReplicaFetcherThread.processPartitionData() should throw KafkaStorageException if replica is offline

Dong Lin created KAFKA-5864: --- Summary: ReplicaFetcherThread.processPartitionData() should throw KafkaStorageException if replica is offline Key: KAFKA-5864 URL: https://issues.apache.org/jira/browse/KAFKA-5864

[jira] [Commented] (KAFKA-5852) Add filter, filterNot, mapValues and Materialized to KTable

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

[jira] [Updated] (KAFKA-5862) Remove ZK dependency from Streams reset tool

[ https://issues.apache.org/jira/browse/KAFKA-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5862: --- Affects Version/s: 0.11.0.0 > Remove ZK dependency from Streams reset tool >

[jira] [Commented] (KAFKA-5861) KStream close( withTimeout ) - does not work under load conditions in the multithreaded KStream application

[ https://issues.apache.org/jira/browse/KAFKA-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159318#comment-16159318 ] Seweryn Habdank-Wojewodzki commented on KAFKA-5861: --- Relates to: KAFKA-4366 > KStream

[jira] [Updated] (KAFKA-5861) KStream close( withTimeout ) - does not work under load conditions in the multithreaded KStream application

[ https://issues.apache.org/jira/browse/KAFKA-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated KAFKA-5861: -- Description: Recently implemented close( withTimeout ) for streams does

[jira] [Updated] (KAFKA-5861) KStream close( withTimeout ) - does not work under load conditions in the multithreaded KStream application

[ https://issues.apache.org/jira/browse/KAFKA-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated KAFKA-5861: -- Summary: KStream close( withTimeout ) - does not work under load

[jira] [Created] (KAFKA-5862) Remove ZK dependency from Streams reset tool

Matthias J. Sax created KAFKA-5862: -- Summary: Remove ZK dependency from Streams reset tool Key: KAFKA-5862 URL: https://issues.apache.org/jira/browse/KAFKA-5862 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-5790) SocketServer.processNewResponses should not skip a response if exception is thrown

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

[jira] [Commented] (KAFKA-5742) Support passing ZK chroot in system tests

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

[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=16158945#comment-16158945 ] ASF GitHub Bot commented on KAFKA-5797: --- Github user guozhangwang closed the pull request at:

[jira] [Commented] (KAFKA-5857) Excessive heap usage on controller node during reassignment

[ https://issues.apache.org/jira/browse/KAFKA-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158933#comment-16158933 ] Onur Karaman commented on KAFKA-5857: - I wouldn't be surprised if there were no attempts so far at

[jira] [Created] (KAFKA-5860) Prevent non-consecutive partition ids

Tom Bentley created KAFKA-5860: -- Summary: Prevent non-consecutive partition ids Key: KAFKA-5860 URL: https://issues.apache.org/jira/browse/KAFKA-5860 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-5857) Excessive heap usage on controller node during reassignment

[ https://issues.apache.org/jira/browse/KAFKA-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158905#comment-16158905 ] Raoufeh Hashemian commented on KAFKA-5857: -- Also I should add that I just realized a subset of

[jira] [Resolved] (KAFKA-2319) After controlled shutdown: IllegalStateException: Kafka scheduler has not been started

[ https://issues.apache.org/jira/browse/KAFKA-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2319. -- Resolution: Fixed This was fixed in newer versions. Pl reopen if you think the issue still exists >

[jira] [Resolved] (KAFKA-1817) AdminUtils.createTopic vs kafka-topics.sh --create with partitions

[ https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1817. -- Resolution: Fixed Fixed in KAFKA-1737 > AdminUtils.createTopic vs kafka-topics.sh --create with

[jira] [Resolved] (KAFKA-1608) Windows: Error: Could not find or load main class org.apache.zookeeper.server.quorum.QuorumPeerMain

[ https://issues.apache.org/jira/browse/KAFKA-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1608. -- Resolution: Fixed This was fixed in newer versions. Pl reopen if you think the issue still exists >

[jira] [Resolved] (KAFKA-251) The ConsumerStats MBean's PartOwnerStats attribute is a string

[ https://issues.apache.org/jira/browse/KAFKA-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-251. - Resolution: Won't Fix Closing inactive issue as per above comments. > The ConsumerStats MBean's

[jira] [Updated] (KAFKA-5708) Update Jackson dependencies (from 2.8.5 to 2.9.x)

[ https://issues.apache.org/jira/browse/KAFKA-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Stojadinović updated KAFKA-5708: -- Description: -In addition to update: remove deprecated version forcing for

[jira] [Commented] (KAFKA-5857) Excessive heap usage on controller node during reassignment

[ https://issues.apache.org/jira/browse/KAFKA-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158763#comment-16158763 ] Raoufeh Hashemian commented on KAFKA-5857: -- [~tedyu] Corrected the step number, I don`t have the

[jira] [Updated] (KAFKA-5857) Excessive heap usage on controller node during reassignment

[ https://issues.apache.org/jira/browse/KAFKA-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raoufeh Hashemian updated KAFKA-5857: - Description: I was trying to expand our kafka cluster of 6 broker nodes to 12 broker

[jira] [Commented] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158667#comment-16158667 ] Ismael Juma commented on KAFKA-1044: I do think we should use scala-logging since it's the most

[jira] [Commented] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158635#comment-16158635 ] Viktor Somogyi commented on KAFKA-1044: --- Hi [~grussell], currently I need to resolve some merge

[jira] [Commented] (KAFKA-5855) records-lag is always zero

[ https://issues.apache.org/jira/browse/KAFKA-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158559#comment-16158559 ] Manikumar commented on KAFKA-5855: -- I am able to generate some lag. By default, consumer reads from

[jira] [Resolved] (KAFKA-5656) Support bulk attributes request on KafkaMbean where some attributes do not exist

[ https://issues.apache.org/jira/browse/KAFKA-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5656. Resolution: Fixed Fix Version/s: 1.0.0 > Support bulk attributes request on KafkaMbean where

[jira] [Commented] (KAFKA-5656) Support bulk attributes request on KafkaMbean where some attributes do not exist

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

[jira] [Commented] (KAFKA-5846) Use singleton NoOpConsumerRebalanceListener in subscribe() call where listener is not specified

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

[jira] [Assigned] (KAFKA-5846) Use singleton NoOpConsumerRebalanceListener in subscribe() call where listener is not specified

[ https://issues.apache.org/jira/browse/KAFKA-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kamal Chandraprakash reassigned KAFKA-5846: --- Assignee: Kamal Chandraprakash > Use singleton NoOpConsumerRebalanceListener

[jira] [Commented] (KAFKA-4260) Improve documentation of configuration listeners=PLAINTEXT://0.0.0.0:9092

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

[jira] [Commented] (KAFKA-5857) Excessive heap usage on controller node during reassignment

[ https://issues.apache.org/jira/browse/KAFKA-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158528#comment-16158528 ] Ismael Juma commented on KAFKA-5857: cc [~onurkaraman] [~junrao] in case they have thoughts. >

[jira] [Updated] (KAFKA-5857) Excessive heap usage on controller node during reassignment

[ https://issues.apache.org/jira/browse/KAFKA-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5857: --- Labels: reliability (was: ) > Excessive heap usage on controller node during reassignment >

[jira] [Commented] (KAFKA-2700) delete topic should remove the corresponding ACL and configs

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

[jira] [Resolved] (KAFKA-5592) Connection with plain client to SSL-secured broker causes OOM

[ https://issues.apache.org/jira/browse/KAFKA-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5592. -- Resolution: Duplicate Marking this as duplicate of KAFKA-4493. > Connection with plain client to

[jira] [Resolved] (KAFKA-4638) Outdated and misleading link in section "End-to-end Batch Compression"

[ https://issues.apache.org/jira/browse/KAFKA-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4638. -- Resolution: Duplicate Resolving as duplicate of KAFKA-5686. PR Raised for KAFKA-5686 > Outdated and

[jira] [Updated] (KAFKA-4116) Specifying 0.0.0.0 in "listeners" doesn't work

[ https://issues.apache.org/jira/browse/KAFKA-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4116: --- Fix Version/s: (was: 1.0.0) > Specifying 0.0.0.0 in "listeners" doesn't work >

[jira] [Commented] (KAFKA-5850) Py4JJavaError: An error occurred while calling o40.loadClass. : java.lang.ClassNotFoundException: org.apache.spark.streaming.kafka.KafkaUtilsPythonHelper

[ https://issues.apache.org/jira/browse/KAFKA-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158405#comment-16158405 ] Manikumar commented on KAFKA-5850: -- [~saurabhbidwai] This issue is not related to Kafka. You may want to

[jira] [Commented] (KAFKA-5859) Avoid retaining AbstractRequest in RequestChannel.Request

[ https://issues.apache.org/jira/browse/KAFKA-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158330#comment-16158330 ] Ismael Juma commented on KAFKA-5859: As stated in the JIRA description, we only need `AbstractRequest`

[jira] [Commented] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158294#comment-16158294 ] Ismael Juma commented on KAFKA-4740: [~junrao] suggested delaying deserialization in KAFKA-5858.

[jira] [Commented] (KAFKA-5859) Avoid retaining AbstractRequest in RequestChannel.Request

[ https://issues.apache.org/jira/browse/KAFKA-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158279#comment-16158279 ] Ismael Juma commented on KAFKA-5859: The idea is not to store `bodyAndSize`, not mutate it. > Avoid

[jira] [Commented] (KAFKA-5859) Avoid retaining AbstractRequest in RequestChannel.Request

[ https://issues.apache.org/jira/browse/KAFKA-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158229#comment-16158229 ] huxihx commented on KAFKA-5859: --- [~ijuma] Does appending `bodyAndSize = null` in

[jira] [Commented] (KAFKA-5832) Add Consumed class and overloads to StreamBuilder

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