[jira] [Commented] (KAFKA-6106) Postpone normal processing of tasks within a thread until restoration of all tasks have completed

[ https://issues.apache.org/jira/browse/KAFKA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359245#comment-16359245 ] Kamal Chandraprakash commented on KAFKA-6106: - [~guozhang] I was busy in other tasks. I try to

[jira] [Updated] (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:all-tabpanel ] Jeff Widman updated KAFKA-6529: --- Fix Version/s: (was: 1.0.2) 1.0.1 > Broker leaks memory and file descriptors

[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=16359020#comment-16359020 ] Bill Bejeck commented on KAFKA-2967: I don't know why, but I had the impression that Asciidoc was not

[jira] [Commented] (KAFKA-6502) Kafka streams deserialization handler not committing offsets on error records

[ https://issues.apache.org/jira/browse/KAFKA-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358884#comment-16358884 ] Guozhang Wang commented on KAFKA-6502: -- Got it, thanks! I think this is a valid point, we will keep

[jira] [Commented] (KAFKA-6549) Deadlock while processing Controller Events

[ https://issues.apache.org/jira/browse/KAFKA-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358859#comment-16358859 ] Manikumar commented on KAFKA-6549: -- This is not exactly deadlock. ZooKeeperClient requests are getting

[jira] [Commented] (KAFKA-4651) Improve test coverage of Stores

[ https://issues.apache.org/jira/browse/KAFKA-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358817#comment-16358817 ] ASF GitHub Bot commented on KAFKA-4651: --- bbejeck opened a new pull request #4555: KAFKA-4651: [WIP]

[jira] [Updated] (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:all-tabpanel ] Damian Guy updated KAFKA-4879: -- Fix Version/s: (was: 1.1.0) 2.0.0 > KafkaConsumer.position may hang forever when

[jira] [Updated] (KAFKA-5214) Re-add KafkaAdminClient#apiVersions

[ https://issues.apache.org/jira/browse/KAFKA-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-5214: --- Priority: Minor (was: Blocker) Fix Version/s: (was: 1.1.0)

[jira] [Commented] (KAFKA-6549) Deadlock while processing Controller Events

[ https://issues.apache.org/jira/browse/KAFKA-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358729#comment-16358729 ] Ted Yu commented on KAFKA-6549: --- kafka-shutdown-hook didn't hold onto any lock. Can you tell me how the

[jira] [Resolved] (KAFKA-6407) Sink task metrics are the same for all connectors

[ https://issues.apache.org/jira/browse/KAFKA-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Yokota resolved KAFKA-6407. -- Resolution: Duplicate > Sink task metrics are the same for all connectors >

[jira] [Updated] (KAFKA-5575) SchemaBuilder should have a method to clone an existing Schema.

[ https://issues.apache.org/jira/browse/KAFKA-5575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5575: - Labels: needs-kip (was: ) > SchemaBuilder should have a method to clone an existing Schema. >

[jira] [Commented] (KAFKA-6407) Sink task metrics are the same for all connectors

[ https://issues.apache.org/jira/browse/KAFKA-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358714#comment-16358714 ] Robert Yokota commented on KAFKA-6407: -- Yes, I believe so.  I'll resolve it as duplicate. > Sink

[jira] [Comment Edited] (KAFKA-5575) SchemaBuilder should have a method to clone an existing Schema.

[ https://issues.apache.org/jira/browse/KAFKA-5575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358653#comment-16358653 ] Randall Hauch edited comment on KAFKA-5575 at 2/9/18 5:13 PM: -- -[~ewencp], is

[jira] [Comment Edited] (KAFKA-5896) Kafka Connect task threads never interrupted

[ https://issues.apache.org/jira/browse/KAFKA-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358670#comment-16358670 ] Randall Hauch edited comment on KAFKA-5896 at 2/9/18 4:59 PM: -- [~ewencp], do

[jira] [Commented] (KAFKA-5896) Kafka Connect task threads never interrupted

[ https://issues.apache.org/jira/browse/KAFKA-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358670#comment-16358670 ] Randall Hauch commented on KAFKA-5896: -- [~ewencp], do you have any thoughts on this? I know in the

[jira] [Commented] (KAFKA-5575) SchemaBuilder should have a method to clone an existing Schema.

[ https://issues.apache.org/jira/browse/KAFKA-5575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358653#comment-16358653 ] Randall Hauch commented on KAFKA-5575: -- [~ewencp], is this an example of something that we would not

[jira] [Updated] (KAFKA-4159) Allow overriding producer & consumer properties at the connector level

[ https://issues.apache.org/jira/browse/KAFKA-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-4159: - Labels: needs-kip (was: ) > Allow overriding producer & consumer properties at the connector

[jira] [Commented] (KAFKA-6502) Kafka streams deserialization handler not committing offsets on error records

[ https://issues.apache.org/jira/browse/KAFKA-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358638#comment-16358638 ] Soby Chacko commented on KAFKA-6502: Hi Guozhang, your reasonings are correct. However, if I introduce

[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=16358637#comment-16358637 ] Randall Hauch commented on KAFKA-6208: -- [~Satyajit], it might be possible to start scanning

[jira] [Commented] (KAFKA-6407) Sink task metrics are the same for all connectors

[ https://issues.apache.org/jira/browse/KAFKA-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358619#comment-16358619 ] Randall Hauch commented on KAFKA-6407: -- [~rayokota], does this sound like a duplicate of KAFKA-6504?

[jira] [Resolved] (KAFKA-4632) Kafka Connect WorkerSinkTask.closePartitions doesn't handle WakeupException

[ https://issues.apache.org/jira/browse/KAFKA-4632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-4632. -- Resolution: Fixed Fix Version/s: 0.10.0.1 0.10.1.0 I'm going to close

[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=16358600#comment-16358600 ] Randall Hauch commented on KAFKA-6208: -- [~Satyajit], I would argue that anything with the scanning

[jira] [Updated] (KAFKA-6503) Connect: Plugin scan is very slow

[ https://issues.apache.org/jira/browse/KAFKA-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6503: - Fix Version/s: 1.1.0 > Connect: Plugin scan is very slow > - > >

[jira] [Updated] (KAFKA-6503) Connect: Plugin scan is very slow

[ https://issues.apache.org/jira/browse/KAFKA-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6503: - Issue Type: Bug (was: Improvement) > Connect: Plugin scan is very slow >

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

[ https://issues.apache.org/jira/browse/KAFKA-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358415#comment-16358415 ] Dan commented on KAFKA-6547:     I think I've eliminated my client from the problem definition. I start the

[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=16358354#comment-16358354 ] ASF GitHub Bot commented on KAFKA-6529: --- rajinisivaram closed pull request #4517: KAFKA-6529: Stop

[jira] [Updated] (KAFKA-6549) Deadlock while processing Controller Events

[ https://issues.apache.org/jira/browse/KAFKA-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-6549: -- Priority: Blocker (was: Major) Fix Version/s: 1.1.0 Component/s: core >

[jira] [Created] (KAFKA-6551) Unbounded queues in WorkerSourceTask cause OutOfMemoryError

Gunnar Morling created KAFKA-6551: - Summary: Unbounded queues in WorkerSourceTask cause OutOfMemoryError Key: KAFKA-6551 URL: https://issues.apache.org/jira/browse/KAFKA-6551 Project: Kafka

[jira] [Commented] (KAFKA-6550) UpdateMetadataRequest should be lazily created

[ https://issues.apache.org/jira/browse/KAFKA-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358293#comment-16358293 ] ASF GitHub Bot commented on KAFKA-6550: --- huxihx opened a new pull request #4553: KAFKA-6550:

[jira] [Created] (KAFKA-6550) UpdateMetadataRequest should be lazily created

huxihx created KAFKA-6550: - Summary: UpdateMetadataRequest should be lazily created Key: KAFKA-6550 URL: https://issues.apache.org/jira/browse/KAFKA-6550 Project: Kafka Issue Type: Improvement

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

[ https://issues.apache.org/jira/browse/KAFKA-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-6548. - Resolution: Not A Problem Hi [~ppmanikandan...@gmail.com]  it sounds like in principle you know

[jira] [Updated] (KAFKA-6549) Deadlock while processing Controller Events

[ https://issues.apache.org/jira/browse/KAFKA-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-6549: - Summary: Deadlock while processing Controller Events (was: Deadlock in ZookeeperClient while processing

[jira] [Created] (KAFKA-6549) Deadlock in ZookeeperClient while processing Controller Events

Manikumar created KAFKA-6549: Summary: Deadlock in ZookeeperClient while processing Controller Events Key: KAFKA-6549 URL: https://issues.apache.org/jira/browse/KAFKA-6549 Project: Kafka Issue

[jira] [Commented] (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:comment-tabpanel=16358216#comment-16358216 ] Andy Coates commented on KAFKA-3438: Morning. Any reason why you’re email thing to me? On 8 Feb

[jira] [Commented] (KAFKA-6446) KafkaProducer with transactionId endless waits when bootstrap server is down

[ https://issues.apache.org/jira/browse/KAFKA-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358171#comment-16358171 ] huxihx commented on KAFKA-6446: --- [~edosciullo] I tried this way and the fix passed on my local env. Since

[jira] [Commented] (KAFKA-6446) KafkaProducer with transactionId endless waits when bootstrap server is down

[ https://issues.apache.org/jira/browse/KAFKA-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358168#comment-16358168 ] Eduardo Sciullo commented on KAFKA-6446: The same behavior appears for commitTransaction,

[jira] [Commented] (KAFKA-6446) KafkaProducer with transactionId endless waits when bootstrap server is down

[ https://issues.apache.org/jira/browse/KAFKA-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358163#comment-16358163 ] huxihx commented on KAFKA-6446: --- Sounds like it's easy to replace await() with the timed version. However,