[jira] [Resolved] (KAFKA-6849) Add transformValues() method to KTable

[ https://issues.apache.org/jira/browse/KAFKA-6849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6849. -- Resolution: Fixed Fix Version/s: 2.0.0 > Add transformValues() method to KTable >

[jira] [Commented] (KAFKA-6849) Add transformValues() method to KTable

[ https://issues.apache.org/jira/browse/KAFKA-6849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481322#comment-16481322 ] ASF GitHub Bot commented on KAFKA-6849: --- guozhangwang closed pull request #4959: KAFKA-6849: add

[jira] [Commented] (KAFKA-6729) KTable should use user source topics if possible and not create changelog topic

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

[jira] [Updated] (KAFKA-6917) Request handler deadlocks attempting to acquire group metadata lock

[ https://issues.apache.org/jira/browse/KAFKA-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-6917: --- Fix Version/s: 0.11.0.3 > Request handler deadlocks attempting to acquire group metadata lock

[jira] [Resolved] (KAFKA-6917) Request handler deadlocks attempting to acquire group metadata lock

[ https://issues.apache.org/jira/browse/KAFKA-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6917. Resolution: Fixed > Request handler deadlocks attempting to acquire group metadata lock >

[jira] [Commented] (KAFKA-6917) Request handler deadlocks attempting to acquire group metadata lock

[ https://issues.apache.org/jira/browse/KAFKA-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481159#comment-16481159 ] ASF GitHub Bot commented on KAFKA-6917: --- hachikuji closed pull request #5036: KAFKA-6917: Process

[jira] [Updated] (KAFKA-6914) Kafka Connect - Plugins class should have a constructor that can take in parent ClassLoader

[ https://issues.apache.org/jira/browse/KAFKA-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriram KS updated KAFKA-6914: - Fix Version/s: 1.1.1 > Kafka Connect - Plugins class should have a constructor that can take in > parent

[jira] [Comment Edited] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480983#comment-16480983 ] Dong Lin edited comment on KAFKA-6188 at 5/18/18 5:59 PM: -- Kafka currently

[jira] [Commented] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480983#comment-16480983 ] Dong Lin commented on KAFKA-6188: - Kafka currently handles disk failure on a per-disk basis, i.e. if there

[jira] [Updated] (KAFKA-6566) SourceTask#stop() not called after exception raised in poll()

[ https://issues.apache.org/jira/browse/KAFKA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-6566: - Fix Version/s: 0.10.2.2 > SourceTask#stop() not called after exception raised in

[jira] [Resolved] (KAFKA-6566) SourceTask#stop() not called after exception raised in poll()

[ https://issues.apache.org/jira/browse/KAFKA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6566. -- Resolution: Fixed > SourceTask#stop() not called after exception raised in

[jira] [Updated] (KAFKA-6566) SourceTask#stop() not called after exception raised in poll()

[ https://issues.apache.org/jira/browse/KAFKA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-6566: - Reviewer: Ewen Cheslack-Postava > SourceTask#stop() not called after exception

[jira] [Updated] (KAFKA-6566) SourceTask#stop() not called after exception raised in poll()

[ https://issues.apache.org/jira/browse/KAFKA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-6566: - Fix Version/s: 1.1.1 1.0.2 0.11.0.3 >

[jira] [Commented] (KAFKA-6566) SourceTask#stop() not called after exception raised in poll()

[ https://issues.apache.org/jira/browse/KAFKA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480970#comment-16480970 ] ASF GitHub Bot commented on KAFKA-6566: --- ewencp closed pull request #5020: KAFKA-6566: Improve

[jira] [Commented] (KAFKA-5697) StreamThread.shutdown() need to interrupt the stream threads to break the loop

[ https://issues.apache.org/jira/browse/KAFKA-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480849#comment-16480849 ] Matthias J. Sax commented on KAFKA-5697: [~guozhang] [~vvcephei]: should we reopen this issue? >

[jira] [Resolved] (KAFKA-5728) Stopping consumer thread cause loosing message in the partition

[ https://issues.apache.org/jira/browse/KAFKA-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5728. -- Resolution: Auto Closed looks like this is related to spring kafka config issue. must be related to

[jira] [Commented] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480809#comment-16480809 ] Ted Yu commented on KAFKA-6188: --- The above code came from: KAFKA-4763; Handle disk failure for JBOD

[jira] [Created] (KAFKA-6918) Kafka server fails to start with IBM JAVA

Nayana Thorat created KAFKA-6918: Summary: Kafka server fails to start with IBM JAVA Key: KAFKA-6918 URL: https://issues.apache.org/jira/browse/KAFKA-6918 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-5697) StreamThread.shutdown() need to interrupt the stream threads to break the loop

[ https://issues.apache.org/jira/browse/KAFKA-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480778#comment-16480778 ] ASF GitHub Bot commented on KAFKA-5697: --- guozhangwang closed pull request #5035: KAFKA-5697: Revert

[jira] [Commented] (KAFKA-6873) Broker is not returning data including requested offset

[ https://issues.apache.org/jira/browse/KAFKA-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480710#comment-16480710 ] Adam Dratwinski commented on KAFKA-6873: Message format version was 1.1.0 and no compression. >

[jira] [Commented] (KAFKA-6917) Request handler deadlocks attempting to acquire group metadata lock

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

[jira] [Commented] (KAFKA-6873) Broker is not returning data including requested offset

[ https://issues.apache.org/jira/browse/KAFKA-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480703#comment-16480703 ] Ismael Juma commented on KAFKA-6873: Thanks for the report. What is the message format version and was

[jira] [Comment Edited] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480686#comment-16480686 ] M. Manna edited comment on KAFKA-6188 at 5/18/18 2:01 PM: -- [~yuzhih...@gmail.com]

[jira] [Comment Edited] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480686#comment-16480686 ] M. Manna edited comment on KAFKA-6188 at 5/18/18 2:00 PM: -- [~yuzhih...@gmail.com]

[jira] [Commented] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480686#comment-16480686 ] M. Manna commented on KAFKA-6188: - [~yuzhih...@gmail.com] I am constantly having issues here. There are

[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=16480626#comment-16480626 ] Robin Tweedie commented on KAFKA-6199: -- Reading the 1.1 release notes, I suspect the fix was from

[jira] [Created] (KAFKA-6917) Request handler deadlocks attempting to acquire group metadata lock

Rajini Sivaram created KAFKA-6917: - Summary: Request handler deadlocks attempting to acquire group metadata lock Key: KAFKA-6917 URL: https://issues.apache.org/jira/browse/KAFKA-6917 Project: Kafka

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480453#comment-16480453 ] Christoph Schmidt commented on KAFKA-1194: -- (!) The only permanently functioning workaround

[jira] [Resolved] (KAFKA-4091) Unable to produce or consume on any topic

[ https://issues.apache.org/jira/browse/KAFKA-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4091. -- Resolution: Cannot Reproduce {color:#00}Closing inactive issue. Please reopen if you think the

[jira] [Created] (KAFKA-6916) AdminClient does not refresh metadata on broker failure

Rajini Sivaram created KAFKA-6916: - Summary: AdminClient does not refresh metadata on broker failure Key: KAFKA-6916 URL: https://issues.apache.org/jira/browse/KAFKA-6916 Project: Kafka

[jira] [Resolved] (KAFKA-3843) Endless consuming messages in Kafka cluster

[ https://issues.apache.org/jira/browse/KAFKA-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3843. -- Resolution: Auto Closed The Scala consumers have been deprecated and no further work is planned, please

[jira] [Resolved] (KAFKA-3620) Clean up Protocol class.

[ https://issues.apache.org/jira/browse/KAFKA-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3620. -- Resolution: Fixed Closing this as some cleanup done in newer versions.  Please reopen if you think

[jira] [Resolved] (KAFKA-3180) issue for extracting JSON from https web page

[ https://issues.apache.org/jira/browse/KAFKA-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3180. -- Resolution: Not A Problem  I suggest to post these kind of queries to 

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

[ https://issues.apache.org/jira/browse/KAFKA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Tweedie resolved KAFKA-6199. -- Resolution: Fixed Fix Version/s: 1.1.0 We upgraded this single broker to 1.1.0 (keeping

[jira] [Resolved] (KAFKA-1977) Make logEndOffset available in the Zookeeper consumer

[ https://issues.apache.org/jira/browse/KAFKA-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1977. -- Resolution: Auto Closed Closing this as the Scala consumers have been deprecated and no further work is