[jira] [Created] (KAFKA-12712) KRaft: Missing controller.quorom.voters config not properly handled

Magnus Edenhill created KAFKA-12712: --- Summary: KRaft: Missing controller.quorom.voters config not properly handled Key: KAFKA-12712 URL: https://issues.apache.org/jira/browse/KAFKA-12712 Project: Ka

[jira] [Resolved] (KAFKA-9180) Broker won't start with empty log dir

[ https://issues.apache.org/jira/browse/KAFKA-9180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill resolved KAFKA-9180. Resolution: Invalid Turned out to be old client jars making a mess.   > Broker won't star

[jira] [Created] (KAFKA-9180) Broker won't start with empty log dir

Magnus Edenhill created KAFKA-9180: -- Summary: Broker won't start with empty log dir Key: KAFKA-9180 URL: https://issues.apache.org/jira/browse/KAFKA-9180 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-7549) Old ProduceRequest with zstd compression does not return error to client

Magnus Edenhill created KAFKA-7549: -- Summary: Old ProduceRequest with zstd compression does not return error to client Key: KAFKA-7549 URL: https://issues.apache.org/jira/browse/KAFKA-7549 Project: K

[jira] [Resolved] (KAFKA-6885) DescribeConfigs synonyms are are identical to parent entry for BROKER resources

[ https://issues.apache.org/jira/browse/KAFKA-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill resolved KAFKA-6885. Resolution: Invalid > DescribeConfigs synonyms are are identical to parent entry for BROKER

[jira] [Created] (KAFKA-6885) DescribeConfigs synonyms are are identical to parent entry for BROKER resources

Magnus Edenhill created KAFKA-6885: -- Summary: DescribeConfigs synonyms are are identical to parent entry for BROKER resources Key: KAFKA-6885 URL: https://issues.apache.org/jira/browse/KAFKA-6885 Pro

[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-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027366#comment-16027366 ] Magnus Edenhill commented on KAFKA-4340: Since this is a change to the protocol AP

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023668#comment-16023668 ] Magnus Edenhill commented on KAFKA-4340: Generally I would agree, but in this case

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022945#comment-16022945 ] Magnus Edenhill commented on KAFKA-4340: While the idea behind this JIRA is good (

[jira] [Reopened] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill reopened KAFKA-4340: > Change the default value of log.message.timestamp.difference.max.ms to the > same as log.rete

[jira] [Issue Comment Deleted] (KAFKA-4842) Streams integration tests occasionally fail with connection error

[ https://issues.apache.org/jira/browse/KAFKA-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill updated KAFKA-4842: --- Comment: was deleted (was: Happened again on a trunk PR, https://github.com/apache/kafka/pull

[jira] [Updated] (KAFKA-4983) Test failure: kafka.api.ConsumerBounceTest.testSubscribeWhenTopicUnavailable

[ https://issues.apache.org/jira/browse/KAFKA-4983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill updated KAFKA-4983: --- Description: The PR builder encountered this test failure: {{kafka.api.ConsumerBounceTest.test

[jira] [Created] (KAFKA-4983) Test failure: kafka.api.ConsumerBounceTest.testSubscribeWhenTopicUnavailable

Magnus Edenhill created KAFKA-4983: -- Summary: Test failure: kafka.api.ConsumerBounceTest.testSubscribeWhenTopicUnavailable Key: KAFKA-4983 URL: https://issues.apache.org/jira/browse/KAFKA-4983 Projec

[jira] [Commented] (KAFKA-4476) Kafka Streams gets stuck if metadata is missing

[ https://issues.apache.org/jira/browse/KAFKA-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949128#comment-15949128 ] Magnus Edenhill commented on KAFKA-4476: Directed here from KAFKA-4482. Happened

[jira] [Commented] (KAFKA-4842) Streams integration tests occasionally fail with connection error

[ https://issues.apache.org/jira/browse/KAFKA-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948898#comment-15948898 ] Magnus Edenhill commented on KAFKA-4842: Happened again on a trunk PR, https://gi

[jira] [Updated] (KAFKA-4974) System test failure in 0.8.2.2 upgrade tests

[ https://issues.apache.org/jira/browse/KAFKA-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill updated KAFKA-4974: --- Description: The 0.10.2 system test failed in one of the upgrade tests from 0.8.2.2: http://te

[jira] [Created] (KAFKA-4974) System test failure in 0.8.2.2 upgrade tests

Magnus Edenhill created KAFKA-4974: -- Summary: System test failure in 0.8.2.2 upgrade tests Key: KAFKA-4974 URL: https://issues.apache.org/jira/browse/KAFKA-4974 Project: Kafka Issue Type: Bu

[jira] [Commented] (KAFKA-1588) Offset response does not support two requests for the same topic/partition combo

[ https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415000#comment-15415000 ] Magnus Edenhill commented on KAFKA-1588: I see now that this behaviour is infact d

[jira] [Commented] (KAFKA-1588) Offset response does not support two requests for the same topic/partition combo

[ https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414995#comment-15414995 ] Magnus Edenhill commented on KAFKA-1588: Thanks [~ijuma]. But I dont see how the b

[jira] [Commented] (KAFKA-1588) Offset response does not support two requests for the same topic/partition combo

[ https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414868#comment-15414868 ] Magnus Edenhill commented on KAFKA-1588: [~guozhang] Why would this fix require a

[jira] [Created] (KAFKA-3743) kafka-server-start.sh: Unhelpful error message

Magnus Edenhill created KAFKA-3743: -- Summary: kafka-server-start.sh: Unhelpful error message Key: KAFKA-3743 URL: https://issues.apache.org/jira/browse/KAFKA-3743 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3547) Broker does not disconnect client on unknown request

[ https://issues.apache.org/jira/browse/KAFKA-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236783#comment-15236783 ] Magnus Edenhill commented on KAFKA-3547: Fixed in https://github.com/apache/kafka/

[jira] [Created] (KAFKA-3547) Broker does not disconnect client on unknown request

Magnus Edenhill created KAFKA-3547: -- Summary: Broker does not disconnect client on unknown request Key: KAFKA-3547 URL: https://issues.apache.org/jira/browse/KAFKA-3547 Project: Kafka Issue

[jira] [Commented] (KAFKA-3160) Kafka LZ4 framing code miscalculates header checksum

[ https://issues.apache.org/jira/browse/KAFKA-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234610#comment-15234610 ] Magnus Edenhill commented on KAFKA-3160: [~ijuma] It needs to go through slow-path

[jira] [Commented] (KAFKA-3160) Kafka LZ4 framing code miscalculates header checksum

[ https://issues.apache.org/jira/browse/KAFKA-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234245#comment-15234245 ] Magnus Edenhill commented on KAFKA-3160: [~dana.powers] My broker patch adds a new

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206838#comment-15206838 ] Magnus Edenhill commented on KAFKA-3442: librdkafka silently ignores partial messa

[jira] [Created] (KAFKA-3394) Broker fails to parse Null Metadata in OffsetCommit requests

Magnus Edenhill created KAFKA-3394: -- Summary: Broker fails to parse Null Metadata in OffsetCommit requests Key: KAFKA-3394 URL: https://issues.apache.org/jira/browse/KAFKA-3394 Project: Kafka

[jira] [Updated] (KAFKA-3219) Long topic names mess up broker topic state

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill updated KAFKA-3219: --- Description: Seems like the broker doesn't like topic names of 254 chars or more when creatin

[jira] [Created] (KAFKA-3219) Long topic names mess up broker topic state

Magnus Edenhill created KAFKA-3219: -- Summary: Long topic names mess up broker topic state Key: KAFKA-3219 URL: https://issues.apache.org/jira/browse/KAFKA-3219 Project: Kafka Issue Type: Bug

[jira] [Assigned] (KAFKA-3160) Kafka LZ4 framing code miscalculates header checksum

[ https://issues.apache.org/jira/browse/KAFKA-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill reassigned KAFKA-3160: -- Assignee: Magnus Edenhill > Kafka LZ4 framing code miscalculates header checksum >

[jira] [Commented] (KAFKA-1493) Use a well-documented LZ4 compression format and remove redundant LZ4HC option

[ https://issues.apache.org/jira/browse/KAFKA-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119920#comment-15119920 ] Magnus Edenhill commented on KAFKA-1493: [~dana.powers] I can confirm this is the

[jira] [Commented] (KAFKA-2695) Handle null string/bytes protocol primitives

[ https://issues.apache.org/jira/browse/KAFKA-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073886#comment-15073886 ] Magnus Edenhill commented on KAFKA-2695: This blocks kafka-consumer-groups.sh to d

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160927#comment-14160927 ] Magnus Edenhill commented on KAFKA-1367: May I suggest not to change the protocol

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148054#comment-14148054 ] Magnus Edenhill commented on KAFKA-1367: [~guozhang] Yes, KAFKA-1555 looks like a

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143218#comment-14143218 ] Magnus Edenhill commented on KAFKA-1367: Apart from supplying the ISR count and li

[jira] [Commented] (KAFKA-955) After a leader change, messages sent with ack=0 are lost

[ https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746810#comment-13746810 ] Magnus Edenhill commented on KAFKA-955: --- Hi Guozhang, I understand that you might no

[jira] [Commented] (KAFKA-955) After a leader change, messages sent with ack=0 are lost

[ https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746561#comment-13746561 ] Magnus Edenhill commented on KAFKA-955: --- If the producer is sending messages through