[jira] [Updated] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated KAFKA-6777: -- Description: Dears, We already encountered many times problems related

[jira] [Updated] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated KAFKA-6777: -- Description: Dears, We already encountered many times problems related

[jira] [Created] (KAFKA-6778) DescribeConfigs does not return error for non-existent topic

Magnus Edenhill created KAFKA-6778: -- Summary: DescribeConfigs does not return error for non-existent topic Key: KAFKA-6778 URL: https://issues.apache.org/jira/browse/KAFKA-6778 Project: Kafka

[jira] [Commented] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433726#comment-16433726 ] Mickael Maison commented on KAFKA-6777: --- You usually do that via JVM options. For example on

[jira] [Comment Edited] (KAFKA-6052) Windows: Consumers not polling when isolation.level=read_committed

[ https://issues.apache.org/jira/browse/KAFKA-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430366#comment-16430366 ] Veera edited comment on KAFKA-6052 at 4/11/18 7:28 AM: --- Hi Jason Could you please

[jira] [Commented] (KAFKA-6677) Remove EOS producer config max.in.flight.request.per.connection=1

[ https://issues.apache.org/jira/browse/KAFKA-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433723#comment-16433723 ] Jagadesh Adireddi commented on KAFKA-6677: -- Hi [~mjsax], I am thinking to contribute to this

[jira] [Commented] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433863#comment-16433863 ] Seweryn Habdank-Wojewodzki commented on KAFKA-6777: --- One more comment. I see quite often

[jira] [Comment Edited] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433863#comment-16433863 ] Seweryn Habdank-Wojewodzki edited comment on KAFKA-6777 at 4/11/18 12:58 PM:

[jira] [Comment Edited] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433799#comment-16433799 ] Seweryn Habdank-Wojewodzki edited comment on KAFKA-6777 at 4/11/18 12:14 PM:

[jira] [Commented] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433799#comment-16433799 ] Seweryn Habdank-Wojewodzki commented on KAFKA-6777: --- Thanks for comment. The problem

[jira] [Updated] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated KAFKA-6777: -- Attachment: screenshot-1.png > Wrong reaction on Out Of Memory

[jira] [Comment Edited] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433799#comment-16433799 ] Seweryn Habdank-Wojewodzki edited comment on KAFKA-6777 at 4/11/18 12:17 PM:

[jira] [Assigned] (KAFKA-6760) responses not logged properly in controller

[ https://issues.apache.org/jira/browse/KAFKA-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison reassigned KAFKA-6760: - Assignee: Mickael Maison > responses not logged properly in controller >

[jira] [Commented] (KAFKA-6744) MockProducer with transaction enabled doesn't fail on commit if a record was failed

[ https://issues.apache.org/jira/browse/KAFKA-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434357#comment-16434357 ] Pascal Gélinas commented on KAFKA-6744: --- Yeah I could, it's been on the back of my mind but I've

[jira] [Commented] (KAFKA-6447) Add Delegation Token Operations to KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434307#comment-16434307 ] ASF GitHub Bot commented on KAFKA-6447: --- junrao closed pull request #4427: KAFKA-6447: Add

[jira] [Commented] (KAFKA-6677) Remove EOS producer config max.in.flight.request.per.connection=1

[ https://issues.apache.org/jira/browse/KAFKA-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434338#comment-16434338 ] Ismael Juma commented on KAFKA-6677: There is a limit of 5 now btw. > Remove EOS producer config

[jira] [Resolved] (KAFKA-6752) Unclean leader election metric no longer working

[ https://issues.apache.org/jira/browse/KAFKA-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-6752. Resolution: Fixed Fix Version/s: 1.1.1 2.0.0 Merged to trunk and 1.1. > Unclean

[jira] [Updated] (KAFKA-6775) AbstractProcessor created in SimpleBenchmark should call super#init

[ https://issues.apache.org/jira/browse/KAFKA-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6775: --- Labels: easy-fix newbie (was: ) > AbstractProcessor created in SimpleBenchmark should call

[jira] [Updated] (KAFKA-6775) AbstractProcessor created in SimpleBenchmark should call super#init

[ https://issues.apache.org/jira/browse/KAFKA-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6775: --- Component/s: streams > AbstractProcessor created in SimpleBenchmark should call super#init >

[jira] [Commented] (KAFKA-6611) Re-write simple benchmark in system tests with JMXTool

[ https://issues.apache.org/jira/browse/KAFKA-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434326#comment-16434326 ] ASF GitHub Bot commented on KAFKA-6611: --- guozhangwang closed pull request #4744: KAFKA-6611, PART

[jira] [Commented] (KAFKA-6677) Remove EOS producer config max.in.flight.request.per.connection=1

[ https://issues.apache.org/jira/browse/KAFKA-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434363#comment-16434363 ] Matthias J. Sax commented on KAFKA-6677: Thanks for pointing out! So we might actually set the

[jira] [Resolved] (KAFKA-6447) Add Delegation Token Operations to KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-6447. Resolution: Fixed Fix Version/s: 2.0.0 Merged the PR to trunk. > Add Delegation Token Operations to

[jira] [Updated] (KAFKA-6780) log cleaner shouldn't clean messages beyond high watermark

[ https://issues.apache.org/jira/browse/KAFKA-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6780: --- Fix Version/s: 1.1.1 1.2.0 > log cleaner shouldn't clean messages beyond high

[jira] [Created] (KAFKA-6780) log cleaner shouldn't clean messages beyond high watermark

Jun Rao created KAFKA-6780: -- Summary: log cleaner shouldn't clean messages beyond high watermark Key: KAFKA-6780 URL: https://issues.apache.org/jira/browse/KAFKA-6780 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-6780) log cleaner shouldn't clean messages beyond high watermark

[ https://issues.apache.org/jira/browse/KAFKA-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434646#comment-16434646 ] Jun Rao commented on KAFKA-6780: The fix is probably to further bound firstUncleanableDirtyOffset by the

[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=16434478#comment-16434478 ] John Roesler commented on KAFKA-5697: - [~guozhang] From your problem description, it seems like the

[jira] [Created] (KAFKA-6779) Kafka connect JMX metrics returns inconsistent metrics while running multiple connectors

Sairam Polavarapu created KAFKA-6779: Summary: Kafka connect JMX metrics returns inconsistent metrics while running multiple connectors Key: KAFKA-6779 URL: https://issues.apache.org/jira/browse/KAFKA-6779

[jira] [Commented] (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=16434752#comment-16434752 ] Jeremy Custenborder commented on KAFKA-4107: This should be implemented in the REST API. Maybe

[jira] [Commented] (KAFKA-6773) Kafka consumer without group.id crashes when requesting offset on a topic-partition

[ https://issues.apache.org/jira/browse/KAFKA-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434735#comment-16434735 ] ASF GitHub Bot commented on KAFKA-6773: --- hachikuji closed pull request #4851: KAFKA-6773; Allow

[jira] [Resolved] (KAFKA-6773) Kafka consumer without group.id crashes when requesting offset on a topic-partition

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

[jira] [Created] (KAFKA-6781) Transient failure in KafkaAdminClientTest.testDescribeConsumerGroupOffsets

Jason Gustafson created KAFKA-6781: -- Summary: Transient failure in KafkaAdminClientTest.testDescribeConsumerGroupOffsets Key: KAFKA-6781 URL: https://issues.apache.org/jira/browse/KAFKA-6781

[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=16434745#comment-16434745 ] ASF GitHub Bot commented on KAFKA-5697: --- vvcephei opened a new pull request #4855: KAFKA-5697:

[jira] [Commented] (KAFKA-6678) Upgrade dependencies with later release versions

[ https://issues.apache.org/jira/browse/KAFKA-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434768#comment-16434768 ] Ted Yu commented on KAFKA-6678: --- Which release would drop support for Java 7 ? thanks > Upgrade

[jira] [Commented] (KAFKA-6058) KIP-222: Add "describe consumer groups" and "list consumer groups" to KafkaAdminClient

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

[jira] [Commented] (KAFKA-6781) Transient failure in KafkaAdminClientTest.testDescribeConsumerGroupOffsets

[ https://issues.apache.org/jira/browse/KAFKA-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434807#comment-16434807 ] Guozhang Wang commented on KAFKA-6781: -- This transient error is fixed along with

[jira] [Created] (KAFKA-6777) Wrong reaction on Out Of Memory situation

Seweryn Habdank-Wojewodzki created KAFKA-6777: - Summary: Wrong reaction on Out Of Memory situation Key: KAFKA-6777 URL: https://issues.apache.org/jira/browse/KAFKA-6777 Project: Kafka

[jira] [Commented] (KAFKA-6052) Windows: Consumers not polling when isolation.level=read_committed

[ https://issues.apache.org/jira/browse/KAFKA-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434927#comment-16434927 ] Veera commented on KAFKA-6052: -- Hi Jason / Vahid   Can you please update about the release date of 1.1.1 or

[jira] [Comment Edited] (KAFKA-6052) Windows: Consumers not polling when isolation.level=read_committed

[ https://issues.apache.org/jira/browse/KAFKA-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434927#comment-16434927 ] Veera edited comment on KAFKA-6052 at 4/12/18 4:58 AM: --- Hi Jason / Vahid  Can you

[jira] [Commented] (KAFKA-6775) AbstractProcessor created in SimpleBenchmark should call super#init

[ https://issues.apache.org/jira/browse/KAFKA-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434864#comment-16434864 ] Jimin Hsieh commented on KAFKA-6775: If I don't misunderstand, I found

[jira] [Assigned] (KAFKA-6775) AbstractProcessor created in SimpleBenchmark should call super#init

[ https://issues.apache.org/jira/browse/KAFKA-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimin Hsieh reassigned KAFKA-6775: -- Assignee: Jimin Hsieh > AbstractProcessor created in SimpleBenchmark should call super#init >

[jira] [Commented] (KAFKA-6705) producer.send() should not block due to metadata not available

[ https://issues.apache.org/jira/browse/KAFKA-6705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434896#comment-16434896 ] Dong Lin commented on KAFKA-6705: - [~omkreddy] [~ijuma] Thanks for the reference to the previous