Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.6 #10

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2152

See

[jira] [Resolved] (KAFKA-15397) Deserializing produce requests may cause memory leaks when exceptions occur

[ https://issues.apache.org/jira/browse/KAFKA-15397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hudeqi resolved KAFKA-15397. Resolution: Resolved > Deserializing produce requests may cause memory leaks when exceptions occur >

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2151

See

Re: [DISCUSS] KIP-966: Eligible Leader Replicas

Hey Calvin, Thanks for the KIP. This will close some of the gaps in leader election! I has a few questions: *>* *High Watermark can only advance if the ISR size is larger or equal to min.insync.replicas*. For my understanding, will we block replication? Or just the high watermark advancement?

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2150

See

Re: [VOTE] KIP-965: Support disaster recovery between clusters by MirrorMaker

Hi hudeqi, Thanks for the KIP! I think the original behavior (removing WRITE permissions during the sync) is a good default, but is not acceptable in every situation. I think providing a configuration for this behavior is the right idea. I had a few questions: 1. Is this configuration only

[jira] [Resolved] (KAFKA-13327) Preflight validations of connectors leads to 500 responses

[ https://issues.apache.org/jira/browse/KAFKA-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-13327. --- Fix Version/s: 3.7.0 Resolution: Fixed > Preflight validations of connectors leads

[jira] [Resolved] (KAFKA-14875) Implement Wakeup()

[ https://issues.apache.org/jira/browse/KAFKA-14875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-14875. - Fix Version/s: 3.7.0 Resolution: Fixed merged the PR to trunk > Implement Wakeup() >

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2149

See

[jira] [Created] (KAFKA-15418) Update statement on decompression location

Lucia Cerchie created KAFKA-15418: - Summary: Update statement on decompression location Key: KAFKA-15418 URL: https://issues.apache.org/jira/browse/KAFKA-15418 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-15417) JoinWindow does not seem to work properly with a KStream - KStream - LeftJoin()

Victor van den Hoven created KAFKA-15417: Summary: JoinWindow does not seem to work properly with a KStream - KStream - LeftJoin() Key: KAFKA-15417 URL: https://issues.apache.org/jira/browse/KAFKA-15417

[jira] [Created] (KAFKA-15416) Flaky test TopicAdminTest::retryEndOffsetsShouldRetryWhenTopicNotFound

Chris Egerton created KAFKA-15416: - Summary: Flaky test TopicAdminTest::retryEndOffsetsShouldRetryWhenTopicNotFound Key: KAFKA-15416 URL: https://issues.apache.org/jira/browse/KAFKA-15416 Project:

Re: Request: Permissions to contribute to Apache Kafka

Hi Krishna, Thank you for your interest in contributing to Apache Kafka. Your accounts are all set. Let me know if you have any questions. Best, On Tue, Aug 29, 2023 at 4:06 PM Krishna Agarwal < krishna0608agar...@gmail.com> wrote: > Hi, > I would like to propose a KIP and contribute to Apache

Request: Permissions to contribute to Apache Kafka

Hi, I would like to propose a KIP and contribute to Apache Kafka. Can I please be provided with the necessary permissions. Wiki ID: krishna06 Jira ID: krishna06 Regards, Krishna

[jira] [Created] (KAFKA-15415) In Java-client, backoff should be skipped for retried producer-batch for a new leader

Mayank Shekhar Narula created KAFKA-15415: - Summary: In Java-client, backoff should be skipped for retried producer-batch for a new leader Key: KAFKA-15415 URL:

Re: [DISCUSS] KIP-910: Update Source offsets for Source Connectors without producing records

Hi Sagar, > The size of offsets topic can be controlled by > setting appropriate topic retention values and > that is a standard practice in Kafka Kafka Connect enforces the `cleanup.policy` configuration for the offsets topic to be "compact" only (references - [1], [2]), so the topic retention

Kafka jenkins is unavailable now

Hi all, Just found Kafka jenkins is unavailable currently. Filed an INFRA issue: https://issues.apache.org/jira/browse/INFRA-24940 FYI. Thanks. Luke

Re: [REVIEW REQUEST] Move ReassignPartitionsCommandArgsTest to java

Hello, Mickael. Thanks for the reply and reviewing previous patches for this feature :). Just to let all know - I’ve got one approval from non commiter. So, if any committer has spare cycle, please, join the simple review that will help to rewrite tools in java

Re: Need Access to create KIP & Jira Tickets

Hi Raghu, Thanks for your interest in Apache Kafka. As Justine rightly points out, for the change of the Jira ID you should file a Jira issue under the INFRA project [1]. If you end up creating another account, I would also recommend creating a Jira issue under INFRA to merge the 2 accounts.