Re: [DISCUSS] Apache Kafka 3.2.0 release

Thanks Bruno! +1 Luke On Sat, Feb 5, 2022 at 10:50 AM Guozhang Wang wrote: > Thanks Bruno! +1 > > On Fri, Feb 4, 2022 at 4:14 PM Ismael Juma wrote: > > > Thanks for volunteering, Bruno. +1! > > > > Ismael > > > > On Fri, Feb 4, 2022 at 7:03 AM Bruno Cadonna wrote: > > > > > Hi, > > > > > >

[jira] [Resolved] (KAFKA-13346) Kafka Streams fails due to RocksDB Locks Not Available Exception

[ https://issues.apache.org/jira/browse/KAFKA-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-13346. --- Resolution: Not A Problem > Kafka Streams fails due to RocksDB Locks Not Available

Re: [DISCUSS] Apache Kafka 3.2.0 release

Thanks Bruno! +1 On Fri, Feb 4, 2022 at 4:14 PM Ismael Juma wrote: > Thanks for volunteering, Bruno. +1! > > Ismael > > On Fri, Feb 4, 2022 at 7:03 AM Bruno Cadonna wrote: > > > Hi, > > > > I'd like to volunteer to be the release manager for our next > > feature release, 3.2.0. If there are no

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

See

Re: [DISCUSS] Apache Kafka 3.2.0 release

Thanks for volunteering, Bruno. +1! Ismael On Fri, Feb 4, 2022 at 7:03 AM Bruno Cadonna wrote: > Hi, > > I'd like to volunteer to be the release manager for our next > feature release, 3.2.0. If there are no objections, I'll send > out the release plan soon. > > Best, > Bruno >

Re: [DISCUSS] Apache Kafka 3.2.0 release

+1 thanks for taking this on. On Fri, Feb 4, 2022 at 11:51 AM Bill Bejeck wrote: > +1. Thanks for volunteering to run the release, Bruno! > > -Bill > > On Fri, Feb 4, 2022 at 10:18 AM David Jacot wrote: > > > +1. Thanks for volunteering, Bruno! > > > > Le ven. 4 févr. 2022 à 16:03, Bruno

[jira] [Resolved] (KAFKA-13322) Java client produces a large amount of garbage during a poll

[ https://issues.apache.org/jira/browse/KAFKA-13322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michail resolved KAFKA-13322. - Resolution: Won't Fix Having done the analysis the changes required to achieve this are far too

Re: [DISCUSS] KIP-704: Send a hint to broker if it is an unclean leader

David Jacot wrote: > The behavior of the leader is clear. However, the part which is > not clear to me is how followers which could get fetch requests > from consumers as well will handle them. Sorry if I was not clear. Got it. I updated the KIP to add more information regarding how the topic

[jira] [Resolved] (KAFKA-13193) Replica manager doesn't update partition state when transitioning from leader to follower with unknown leader

[ https://issues.apache.org/jira/browse/KAFKA-13193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-13193. -- Resolution: Fixed > Replica manager doesn't update partition state when transitioning from

Re: [DISCUSS] KIP-816: Topology changes without local state reset

Hi folks, I think the NamedTopology work would help with the convenience of the solution for this KIP, but I feel it is not by itself the solution here. If I'm not mistaken, the scope of this KIP is trying to tackle that, *assuming the developer already knows* a new topology or part of the

[jira] [Created] (KAFKA-13646) Implement KIP-801: KRaft authorizer

Colin McCabe created KAFKA-13646: Summary: Implement KIP-801: KRaft authorizer Key: KAFKA-13646 URL: https://issues.apache.org/jira/browse/KAFKA-13646 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-12421) Improve controller's atomic grouping

[ https://issues.apache.org/jira/browse/KAFKA-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-12421. -- Assignee: Jose Armando Garcia Sancio (was: HaiyuanZhao) Resolution: Fixed > Improve

[jira] [Resolved] (KAFKA-12214) Generated code does not include UUID or struct fields in its toString output

[ https://issues.apache.org/jira/browse/KAFKA-12214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-12214. -- Resolution: Fixed > Generated code does not include UUID or struct fields in its toString

[jira] [Resolved] (KAFKA-12271) Expose consistent Raft metadata to components

[ https://issues.apache.org/jira/browse/KAFKA-12271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-12271. -- Fix Version/s: 3.0.0 Resolution: Fixed > Expose consistent Raft metadata to components

[jira] [Resolved] (KAFKA-12209) Add the timeline data structures for the KIP-631 controller

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

[jira] [Resolved] (KAFKA-10724) Command to run single quorum in raft is missing "--config" parameters.

[ https://issues.apache.org/jira/browse/KAFKA-10724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-10724. -- Resolution: Fixed > Command to run single quorum in raft is missing "--config" parameters. >

[jira] [Resolved] (KAFKA-9154) ProducerId generation should be managed by the Controller

[ https://issues.apache.org/jira/browse/KAFKA-9154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-9154. - Fix Version/s: 3.1.0 Resolution: Fixed We implemented KIP-730 in Kafka 3.1. Closing this.

[jira] [Resolved] (KAFKA-13503) Validate broker configs for KRaft

[ https://issues.apache.org/jira/browse/KAFKA-13503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-13503. -- Fix Version/s: 3.2.0 Reviewer: Jose Armando Garcia Sancio Assignee: Colin

Re: [VOTE] KIP-801 new authorizer for kip-500 kraft mode

Hi all, The vote is now closed. KIP-801 has been approved with 3 binding +1s from Jason Gustafson, Manikumar Reddy, and David Arthur. Thanks, all. Colin On Wed, Feb 2, 2022, at 16:14, Colin McCabe wrote: > Thanks, Manikumar. Together with Jason and David's votes (David's vote > is in the

Re: [DISCUSS] Apache Kafka 3.2.0 release

+1. Thanks for volunteering to run the release, Bruno! -Bill On Fri, Feb 4, 2022 at 10:18 AM David Jacot wrote: > +1. Thanks for volunteering, Bruno! > > Le ven. 4 févr. 2022 à 16:03, Bruno Cadonna a écrit : > > > Hi, > > > > I'd like to volunteer to be the release manager for our next > >

Re: [DISCUSS] KIP-817: Fix inconsistency in dynamic application log levels

Hi Dongjin, Thanks for the KIP. It is not so clear to me why we decided not to support OFF in the first place. I understand that entirely disabling a logger is rare. I find the KIP a bit week at the moment for two reasons: 1) The KIP says that the levels that we use are not fully consistent

Re: [DISCUSS] KIP-792: Add "generation" field into consumer protocol

Hi Luke, Thanks for updating the KIP. I just have a minor request. Could you fully describe the changes to the Subscription public class in the KIP? I think that it would be better than just saying that the generation will be added to id. Otherwise, the KIP LGTM. Thanks, David On Mon, Nov 29,

Re: [DISCUSS] Apache Kafka 3.2.0 release

+1. Thanks for volunteering, Bruno! Le ven. 4 févr. 2022 à 16:03, Bruno Cadonna a écrit : > Hi, > > I'd like to volunteer to be the release manager for our next > feature release, 3.2.0. If there are no objections, I'll send > out the release plan soon. > > Best, > Bruno >

[DISCUSS] Apache Kafka 3.2.0 release

Hi, I'd like to volunteer to be the release manager for our next feature release, 3.2.0. If there are no objections, I'll send out the release plan soon. Best, Bruno

Re: [DISCUSS] KIP-816: Topology changes without local state reset

Hi Guozhang, Sophie, Thanks for both taking the time to review my proposal. I did actually see the NamedTopology classes, and noted that they were internal. I didn't realise they are part of an intended solution to this problem, that's very interesting. I'm going to try to find some time to take

Re: [DISCUSS] KIP-818: Introduce cache-size-bytes-total Task Level Metric

Thanks Sophie/Guozhang. Yeah I could have amended the KIP but it slipped my mind when Guozhang proposed this in the PR. Later on, the PR was merged and KIP was marked as adopted so I thought I will write a new one. I know the PR had been reopened now :p . I dont have much preference on a new KIP

Re: [DISCUSS] KIP-816: Topology changes without local state reset

Hey Nick, thanks for the KIP, this is definitely a much-needed feature. I've actually been working on a somewhat similar feature for a while now and have a good chunk of the implementation completed -- but so far it's only exposed via internal APIs and hasn't been brought to a KIP yet, as it's a