[jira] [Created] (KAFKA-12789) Remove Stale comments for meta response handling logic

HaiyuanZhao created KAFKA-12789: --- Summary: Remove Stale comments for meta response handling logic Key: KAFKA-12789 URL: https://issues.apache.org/jira/browse/KAFKA-12789 Project: Kafka Issue

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

See

Re: [DISCUSS] KIP-709: Extend OffsetFetch requests to accept multiple group ids

Hi Everyone, I’ve begun working on this KIP now and found that another class will be needing public changes. I have updated the KIP to reflect this, so just wanted to update the dev list as well. You can find the updated KIP here: 

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

See

[jira] [Created] (KAFKA-12788) Improve KRaft replica placement

Colin McCabe created KAFKA-12788: Summary: Improve KRaft replica placement Key: KAFKA-12788 URL: https://issues.apache.org/jira/browse/KAFKA-12788 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-12471) Implement createPartitions in KIP-500 mode

[ https://issues.apache.org/jira/browse/KAFKA-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-12471. -- Fix Version/s: 3.0.0 Resolution: Fixed > Implement createPartitions in KIP-500 mode >

[jira] [Resolved] (KAFKA-12334) Add the KIP-631 metadata shell

[ https://issues.apache.org/jira/browse/KAFKA-12334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-12334. -- Fix Version/s: 2.8.0 Resolution: Fixed Added in 2.8 > Add the KIP-631 metadata shell

[jira] [Resolved] (KAFKA-12275) KIP-500: Remove controllerOnly restriction from the DecommissionBroker API

[ https://issues.apache.org/jira/browse/KAFKA-12275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-12275. -- Fix Version/s: 2.8.0 Assignee: Colin McCabe Resolution: Fixed

[jira] [Created] (KAFKA-12787) Configure and integrate controller snapshot with the RaftClient

Jose Armando Garcia Sancio created KAFKA-12787: -- Summary: Configure and integrate controller snapshot with the RaftClient Key: KAFKA-12787 URL: https://issues.apache.org/jira/browse/KAFKA-12787

[jira] [Resolved] (KAFKA-12754) TaskMetadata endOffsets does not update when the offsets are read

[ https://issues.apache.org/jira/browse/KAFKA-12754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-12754. Fix Version/s: 3.0.0 Resolution: Fixed > TaskMetadata endOffsets

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

See

Re: [DISCUSS] KIP-731: Record Rate Limiting for Kafka Connect

Hey y'all, I've expanded the scope of this KIP slightly to include a pluggable interface, RateLimiter. After implementing this a few different ways, it's clear that the configuration story is actually simpler with a pluggable model. Out-of-the-box, we have just two configuration properties to

Re: [VOTE] KIP-740: Use TaskId instead of String for the taskId field in TaskMetadata

Thanks for these updates, Sophie, Unfortunately, I have some minor suggestions: 1. "Topic Group" is a vestigial term from the early days of the codebase. We call a "topic group" a "subtopology" in the public interface now (although "topic group" is still used internally some places). For

Re: [DISCUSS] KIP-618: Atomic commit of source connector records and offsets

Hi Tom, Really interesting turn this has taken! Responses inline. > I'm not quite sure I follow what you mean here. Can you explain? AFAICT it doesn't apply in a cluster where all tasks are using fencible producers, but maybe I'm missing something. Imagine this (unlikely but possible) scenario:

Re: [DISCUSS] KIP-739: Block Less on KafkaProducer#send

Makes sense! Ryanne On Fri, May 14, 2021, 9:39 AM Nakamura wrote: > Hey Ryanne, > > I see what you're saying about serde blocking, but I think we should > consider it out of scope for this patch. Right now we've nailed down a > couple of use cases where we can unambiguously say, "I can make

Re: [DISCUSS] KIP-739: Block Less on KafkaProducer#send

Hey Ryanne, I see what you're saying about serde blocking, but I think we should consider it out of scope for this patch. Right now we've nailed down a couple of use cases where we can unambiguously say, "I can make progress now" or "I cannot make progress now", which makes it possible to

Re: [DISCUSS] KIP-618: Atomic commit of source connector records and offsets

Hi Chris, Thanks for the reply. "required"/"requested" sounds good to me. Likewise the pre-flight check and "PUT /{connectorType}/config/validate". The other half is we'd still need to > track the number of tasks for that connector that would need to be fenced > out if/when exactly-once for it

[jira] [Created] (KAFKA-12786) Getting SslTransportLayerTest error

Sibelle created KAFKA-12786: --- Summary: Getting SslTransportLayerTest error Key: KAFKA-12786 URL: https://issues.apache.org/jira/browse/KAFKA-12786 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-12784) ssl kafka failed

Trofimov created KAFKA-12784: Summary: ssl kafka failed Key: KAFKA-12784 URL: https://issues.apache.org/jira/browse/KAFKA-12784 Project: Kafka Issue Type: Task Components: config,

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

See