[jira] [Created] (KAFKA-18672) CoordinatorRecordSerde must validate value versions

David Jacot created KAFKA-18672: --- Summary: CoordinatorRecordSerde must validate value versions Key: KAFKA-18672 URL: https://issues.apache.org/jira/browse/KAFKA-18672 Project: Kafka Issue Type:

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.9 #157

See

Jenkins build is still unstable: Kafka » Kafka PowerPC Daily » test-powerpc #194

See

[jira] [Created] (KAFKA-18671) Failed handling of fetch response should log an error message

José Armando García Sancio created KAFKA-18671: -- Summary: Failed handling of fetch response should log an error message Key: KAFKA-18671 URL: https://issues.apache.org/jira/browse/KAFKA-18671

[jira] [Resolved] (KAFKA-15944) Flaky test - verifyStore[cache=false, log=true, supplier=ROCKS_KV, kind=DSL] – org.apache.kafka.streams.integration.PositionRestartIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-15944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-15944. - Resolution: Cannot Reproduce This ticket is over a year old. Looking into recent test hi

[jira] [Created] (KAFKA-18670) Update Netty dependency to fix CVE-2024-47535

Jonathan Lopez created KAFKA-18670: -- Summary: Update Netty dependency to fix CVE-2024-47535 Key: KAFKA-18670 URL: https://issues.apache.org/jira/browse/KAFKA-18670 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-18669) Connector is restarted before it is started

Anil Dasari created KAFKA-18669: --- Summary: Connector is restarted before it is started Key: KAFKA-18669 URL: https://issues.apache.org/jira/browse/KAFKA-18669 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-18442) Downgrades to 3.3.2 will fail from versions 3.6.0 and above when JBOD is enabled

[ https://issues.apache.org/jira/browse/KAFKA-18442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-18442. -- Resolution: Won't Fix So firstly, this is a real bug, which we cannot fix since 3.3 is no long

[jira] [Resolved] (KAFKA-18498) Kafka Streams main thread does not release lock

[ https://issues.apache.org/jira/browse/KAFKA-18498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-18498. - Resolution: Fixed > Kafka Streams main thread does not release lock > --

[jira] [Resolved] (KAFKA-18668) config/kraft/reconfig-server.properties no longer exists in quickstart

[ https://issues.apache.org/jira/browse/KAFKA-18668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18668. - Resolution: Implemented [~mimaison] : Thanks for the info. That PR covers this need. Closing this jira.

[jira] [Created] (KAFKA-18668) config/kraft/reconfig-server.properties no longer exists in quickstart

Jun Rao created KAFKA-18668: --- Summary: config/kraft/reconfig-server.properties no longer exists in quickstart Key: KAFKA-18668 URL: https://issues.apache.org/jira/browse/KAFKA-18668 Project: Kafka

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.9 #156

See

[jira] [Resolved] (KAFKA-18383) Remove reserved.broker.max.id and broker.id.generation.enable

[ https://issues.apache.org/jira/browse/KAFKA-18383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18383. Resolution: Fixed trunk:   https://github.com/apache/kafka/commit/4dd0bcbde85a599a22a41db2

reviving KIP-723: Add socket.tcp.no.delay property to Kafka Config

hello! There was some work done on KIP-723 to propose to avoid setting TCP_NODELAY on all sockets. The metrics provided at the time were showing a great reduction of packets per second in one usecase. I am running Kafka on Kubernetes and see some of the nodes getting overloaded with the amount of p

[jira] [Resolved] (KAFKA-18662) Return CONCURRENT_TRANSACTIONS on produce request for TV2

[ https://issues.apache.org/jira/browse/KAFKA-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-18662. Resolution: Fixed > Return CONCURRENT_TRANSACTIONS on produce request for TV2 > --

[jira] [Created] (KAFKA-18667) Add ducktape tests for simultaneous broker + controller failure

Kevin Wu created KAFKA-18667: Summary: Add ducktape tests for simultaneous broker + controller failure Key: KAFKA-18667 URL: https://issues.apache.org/jira/browse/KAFKA-18667 Project: Kafka Issu

[jira] [Resolved] (KAFKA-18632) ShareConsumerTest multibroker tests

[ https://issues.apache.org/jira/browse/KAFKA-18632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18632. -- Fix Version/s: 4.1.0 Resolution: Fixed > ShareConsumerTest multibroker tests >

[jira] [Created] (KAFKA-18666) Controller-side monitoring for broker shutdown and startup

Kevin Wu created KAFKA-18666: Summary: Controller-side monitoring for broker shutdown and startup Key: KAFKA-18666 URL: https://issues.apache.org/jira/browse/KAFKA-18666 Project: Kafka Issue Type

[jira] [Resolved] (KAFKA-18653) Fix mocks and potential thread leak issues causing silent RejectedExecutionException

[ https://issues.apache.org/jira/browse/KAFKA-18653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18653. -- Fix Version/s: 4.1.0 Resolution: Fixed > Fix mocks and potential thread leak is

Re: [DISCUSS] KIP-1097: error record reporter

Bumping the thread On Mon, Jan 13, 2025 at 2:18 PM Anton Liauchuk wrote: > Trying to bump once more > > On Wed, Dec 11, 2024 at 4:02 PM Anton Liauchuk > wrote: > >> Bumping the thread >> >> On Sun, Dec 1, 2024 at 8:33 AM Anton Liauchuk >> wrote: >> >>> Hi >>> Thank you for your feedback. >>>

[jira] [Resolved] (KAFKA-18633) Remove errorUnavailableEndpoints from handleTopicMetadataRequest

[ https://issues.apache.org/jira/browse/KAFKA-18633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18633. Resolution: Invalid v0 is not removed now, so this ticket is invalid > Remove errorUnavai

[jira] [Resolved] (KAFKA-18663) Metadata v0-v3 should be undeprecated

[ https://issues.apache.org/jira/browse/KAFKA-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-18663. - Resolution: Fixed > Metadata v0-v3 should be undeprecated >

[jira] [Created] (KAFKA-18665) Controller quorum error when initializing cluster instance

Sushant Mahajan created KAFKA-18665: --- Summary: Controller quorum error when initializing cluster instance Key: KAFKA-18665 URL: https://issues.apache.org/jira/browse/KAFKA-18665 Project: Kafka

[jira] [Resolved] (KAFKA-18664) dockerfile should not rely on the public archive

[ https://issues.apache.org/jira/browse/KAFKA-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] TengYao Chi resolved KAFKA-18664. - Resolution: Fixed > dockerfile should not rely on the public archive > -

[jira] [Created] (KAFKA-18664) dockerfile should not rely on the public archive

TengYao Chi created KAFKA-18664: --- Summary: dockerfile should not rely on the public archive Key: KAFKA-18664 URL: https://issues.apache.org/jira/browse/KAFKA-18664 Project: Kafka Issue Type: Im

Re: [DISCUSS] KIP-1126: Serialize changes to Kafka with a build queue

Hi David, Thanks for this and for your work improving the Kafka CI. I have a question: A problem was mentioned about two PRs acting against each other when there’s no delay and being merged concurrently. Wouldn’t this still happen in the queue with concurrent merging as well? Best Regards, Uchec