[jira] [Updated] (KAFKA-7684) kafka consumer SchemaException occurred: Error reading field 'brokers':

[ https://issues.apache.org/jira/browse/KAFKA-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leibo updated KAFKA-7684: - Description: kafka consumer occurred org.apache.kafka.common.protocol.types.SchemaException: Error reading

[jira] [Created] (KAFKA-7679) With acks=all a single "stuck" non-leader replica can cause a timeout

Corentin Chary created KAFKA-7679: - Summary: With acks=all a single "stuck" non-leader replica can cause a timeout Key: KAFKA-7679 URL: https://issues.apache.org/jira/browse/KAFKA-7679 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=16700533#comment-16700533 ] lkgen commented on KAFKA-1194: -- Hi, if you are interested on a more complete approach for the problem you

[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=16700692#comment-16700692 ] Hans Schuell commented on KAFKA-6188: - I have also a Confluent 5.0.0 (Kafka 2.0.0) test system on

[jira] [Issue Comment Deleted] (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:all-tabpanel ] LiorK updated KAFKA-1194: - Comment: was deleted (was: I have some code that appears to solve the problem on Windows, including the

[jira] [Resolved] (KAFKA-7508) Kafka broker anonymous disconnected from Zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Santilli resolved KAFKA-7508. -- Resolution: Not A Problem Closed since was requested by the reported. Sathish agree

[jira] [Comment Edited] (KAFKA-7504) Broker performance degradation caused by call of sendfile reading disk in network thread

[ https://issues.apache.org/jira/browse/KAFKA-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700785#comment-16700785 ] Hugh O'Brien edited comment on KAFKA-7504 at 11/27/18 5:46 PM: --- [~guozhang]

[jira] [Commented] (KAFKA-7504) Broker performance degradation caused by call of sendfile reading disk in network thread

[ https://issues.apache.org/jira/browse/KAFKA-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700785#comment-16700785 ] Hugh O'Brien commented on KAFKA-7504: - [~guozhang] that's an interesting suggestion, as long as the

[jira] [Resolved] (KAFKA-7367) Streams should not create state store directories unless they are needed

[ https://issues.apache.org/jira/browse/KAFKA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7367. Resolution: Fixed Fix Version/s: 2.2.0 > Streams should not create state store

[jira] [Commented] (KAFKA-7660) Stream Metrics - Memory Analysis

[ https://issues.apache.org/jira/browse/KAFKA-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701043#comment-16701043 ] John Roesler commented on KAFKA-7660: - Hey [~pkleindl], I'll get you a PR to test asap. No, we

[jira] [Created] (KAFKA-7680) fetching a refilled chunk of log can cause log divergence

Jun Rao created KAFKA-7680: -- Summary: fetching a refilled chunk of log can cause log divergence Key: KAFKA-7680 URL: https://issues.apache.org/jira/browse/KAFKA-7680 Project: Kafka Issue Type: Bug

[jira] [Comment Edited] (KAFKA-7509) Kafka Connect logs unnecessary warnings about unused configurations

[ https://issues.apache.org/jira/browse/KAFKA-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16673834#comment-16673834 ] Randall Hauch edited comment on KAFKA-7509 at 11/27/18 9:12 PM: Since

[jira] [Commented] (KAFKA-7367) Streams should not create state store directories unless they are needed

[ https://issues.apache.org/jira/browse/KAFKA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701041#comment-16701041 ] ASF GitHub Bot commented on KAFKA-7367: --- mjsax closed pull request #5696: KAFKA-7367: Streams

[jira] [Commented] (KAFKA-7680) fetching a refilled chunk of log can cause log divergence

[ https://issues.apache.org/jira/browse/KAFKA-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701084#comment-16701084 ] Jun Rao commented on KAFKA-7680: One way to fix this is the following. We already include the expected

[jira] [Commented] (KAFKA-7597) Trogdor - Support transactions in ProduceBenchWorker

[ https://issues.apache.org/jira/browse/KAFKA-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701009#comment-16701009 ] ASF GitHub Bot commented on KAFKA-7597: --- cmccabe closed pull request #5885: KAFKA-7597: Make

[jira] [Commented] (KAFKA-7223) KIP-328: Add in-memory Suppression

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

[jira] [Created] (KAFKA-7682) turning on request logging for a subset of request types

Jun Rao created KAFKA-7682: -- Summary: turning on request logging for a subset of request types Key: KAFKA-7682 URL: https://issues.apache.org/jira/browse/KAFKA-7682 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-7660) Stream Metrics - Memory Analysis

[ https://issues.apache.org/jira/browse/KAFKA-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701100#comment-16701100 ] John Roesler commented on KAFKA-7660: - ok [~pkleindl], I think that

[jira] [Commented] (KAFKA-7660) Stream Metrics - Memory Analysis

[ https://issues.apache.org/jira/browse/KAFKA-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701096#comment-16701096 ] ASF GitHub Bot commented on KAFKA-7660: --- vvcephei opened a new pull request #5953: KAFKA-7660: fix

[jira] [Commented] (KAFKA-7671) A KStream/GlobalKTable join shouldn't reset the repartition flag

[ https://issues.apache.org/jira/browse/KAFKA-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701203#comment-16701203 ] Andy Bryant commented on KAFKA-7671: Hi [~mjsax], I just checked the old versions (1.1, 1.0, 0.11,

[jira] [Created] (KAFKA-7681) new metric for request thread utilization by request type

Jun Rao created KAFKA-7681: -- Summary: new metric for request thread utilization by request type Key: KAFKA-7681 URL: https://issues.apache.org/jira/browse/KAFKA-7681 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-7389) Upgrade spotBugs for Java 11 support

[ https://issues.apache.org/jira/browse/KAFKA-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701130#comment-16701130 ] ASF GitHub Bot commented on KAFKA-7389: --- ijuma closed pull request #5943: KAFKA-7389: Enable

[jira] [Updated] (KAFKA-7683) Support ConfigDef.Type.MAP

[ https://issues.apache.org/jira/browse/KAFKA-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Czajka updated KAFKA-7683: --- Issue Type: Improvement (was: Bug) > Support ConfigDef.Type.MAP > -- > >

[jira] [Created] (KAFKA-7683) Support ConfigDef.Type.MAP

Paul Czajka created KAFKA-7683: -- Summary: Support ConfigDef.Type.MAP Key: KAFKA-7683 URL: https://issues.apache.org/jira/browse/KAFKA-7683 Project: Kafka Issue Type: Bug Components:

[jira] [Commented] (KAFKA-7683) Support ConfigDef.Type.MAP

[ https://issues.apache.org/jira/browse/KAFKA-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701291#comment-16701291 ] Ryanne Dolan commented on KAFKA-7683: - You can use originalsWithPrefix() to get back a map from

[jira] [Commented] (KAFKA-7653) Streams-Scala: Add type level differentiation for Key and Value serdes.

[ https://issues.apache.org/jira/browse/KAFKA-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701345#comment-16701345 ] Guozhang Wang commented on KAFKA-7653: -- I think [~mark.tranter] is trying to provide a work-around

[jira] [Updated] (KAFKA-7678) Failed to close producer due to java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah updated KAFKA-7678: Component/s: streams > Failed to close producer due to java.lang.NullPointerException >

[jira] [Commented] (KAFKA-7681) new metric for request thread utilization by request type

[ https://issues.apache.org/jira/browse/KAFKA-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701387#comment-16701387 ] Mayuresh Gharat commented on KAFKA-7681: Hi [~junrao], This seems more like the Broker Topic

[jira] [Commented] (KAFKA-7671) A KStream/GlobalKTable join shouldn't reset the repartition flag

[ https://issues.apache.org/jira/browse/KAFKA-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701398#comment-16701398 ] Matthias J. Sax commented on KAFKA-7671: Thanks for looking into this [~kiwiandy] > A

[jira] [Commented] (KAFKA-7678) Failed to close producer due to java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701400#comment-16701400 ] Matthias J. Sax commented on KAFKA-7678: Are you saying that the shutdown still finished

[jira] [Updated] (KAFKA-7672) The local state not fully restored after KafkaStream rebalanced, resulting in data loss

[ https://issues.apache.org/jira/browse/KAFKA-7672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-7672: --- Fix Version/s: (was: 2.1.0) > The local state not fully restored after KafkaStream

[jira] [Commented] (KAFKA-7671) A KStream/GlobalKTable join shouldn't reset the repartition flag

[ https://issues.apache.org/jira/browse/KAFKA-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701416#comment-16701416 ] Matthias J. Sax commented on KAFKA-7671: I marked fixed version as 2.2.0 and 2.1.1 for now, to

[jira] [Updated] (KAFKA-7671) A KStream/GlobalKTable join shouldn't reset the repartition flag

[ https://issues.apache.org/jira/browse/KAFKA-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-7671: --- Fix Version/s: 2.1.1 2.2.0 > A KStream/GlobalKTable join shouldn't reset

[jira] [Updated] (KAFKA-7672) The local state not fully restored after KafkaStream rebalanced, resulting in data loss

[ https://issues.apache.org/jira/browse/KAFKA-7672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-7672: --- Fix Version/s: 2.1.1 2.2.0 > The local state not fully restored after

[jira] [Commented] (KAFKA-3184) Add Checkpoint for In-memory State Store

[ https://issues.apache.org/jira/browse/KAFKA-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701422#comment-16701422 ] Matthias J. Sax commented on KAFKA-3184: Just a side comment: RocksDB allows to "pin/freeze" a

[jira] [Resolved] (KAFKA-7620) ConfigProvider is broken for KafkaConnect when TTL is not null

[ https://issues.apache.org/jira/browse/KAFKA-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-7620. -- Resolution: Fixed Fix Version/s: 2.0.2 2.1.1

[jira] [Commented] (KAFKA-5581) Avoid creating changelog topics for state stores that are materialized from a source topic

[ https://issues.apache.org/jira/browse/KAFKA-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701424#comment-16701424 ] Matthias J. Sax commented on KAFKA-5581: [~guozhang] Wasn't the optimization for (1) there since

[jira] [Assigned] (KAFKA-6036) Enable logical materialization to physical materialization

[ https://issues.apache.org/jira/browse/KAFKA-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-6036: -- Assignee: Guozhang Wang > Enable logical materialization to physical materialization

[jira] [Updated] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3705: --- Issue Type: New Feature (was: Bug) > Support non-key joining in KTable >

[jira] [Commented] (KAFKA-7620) ConfigProvider is broken for KafkaConnect when TTL is not null

[ https://issues.apache.org/jira/browse/KAFKA-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701426#comment-16701426 ] ASF GitHub Bot commented on KAFKA-7620: --- ewencp closed pull request #5914: KAFKA-7620: Fix restart

[jira] [Created] (KAFKA-7684) kafka consumer SchemaException occurred: Error reading field 'brokers':

leibo created KAFKA-7684: Summary: kafka consumer SchemaException occurred: Error reading field 'brokers': Key: KAFKA-7684 URL: https://issues.apache.org/jira/browse/KAFKA-7684 Project: Kafka

[jira] [Commented] (KAFKA-7508) Kafka broker anonymous disconnected from Zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700187#comment-16700187 ] Jonathan Santilli commented on KAFKA-7508: -- Kafka Brokers offer good metrics from JMX, you can

[jira] [Commented] (KAFKA-7660) Stream Metrics - Memory Analysis

[ https://issues.apache.org/jira/browse/KAFKA-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700100#comment-16700100 ] Patrik Kleindl commented on KAFKA-7660: --- [~vvcephei] Thanks for confirming, glad I was able to

[jira] [Updated] (KAFKA-7677) Client login with already existing JVM subject

[ https://issues.apache.org/jira/browse/KAFKA-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Somogyi updated KAFKA-7677: - Affects Version/s: 2.2.0 > Client login with already existing JVM subject >

[jira] [Updated] (KAFKA-7678) Failed to close producer due to java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Santilli updated KAFKA-7678: - Description: This occurs when the group is rebalancing in a Kafka Stream application and

[jira] [Created] (KAFKA-7678) Failed to close producer due to java.lang.NullPointerException

Jonathan Santilli created KAFKA-7678: Summary: Failed to close producer due to java.lang.NullPointerException Key: KAFKA-7678 URL: https://issues.apache.org/jira/browse/KAFKA-7678 Project: Kafka

[jira] [Commented] (KAFKA-6635) Producer close does not await pending transaction

[ https://issues.apache.org/jira/browse/KAFKA-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700392#comment-16700392 ] Viktor Somogyi commented on KAFKA-6635: --- [~hachikuji] is this still relevant? Do you mind if I pick