[jira] [Resolved] (KAFKA-13833) Remove the "min_version_level" version from the finalized version range that is written to ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-13833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dengziming resolved KAFKA-13833. Resolution: Fixed > Remove the "min_version_level" version from the finalized version range that

[jira] [Resolved] (KAFKA-12902) Add UINT32 type in generator

[ https://issues.apache.org/jira/browse/KAFKA-12902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dengziming resolved KAFKA-12902. Resolution: Fixed > Add UINT32 type in generator > > >

Re: [DISCUSS] KIP-842: Add richer group offset reset mechanisms

Hi all, Why is no one talking about this? best hudeqi 2022-05-23 17:45:53"胡德祺" <16120...@bjtu.edu.cn>写道： Hi all, I have written a new KIPto add some group offset reset mechanisms. Please take a look here: https://cwiki.apache.org/confluence/x/xhyhD besthudeqi

[jira] [Resolved] (KAFKA-13858) Kraft should not shutdown metadata listener until controller shutdown is finished

[ https://issues.apache.org/jira/browse/KAFKA-13858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-13858. - Fix Version/s: 3.3 Resolution: Fixed > Kraft should not shutdown metadata listene

[jira] [Created] (KAFKA-13940) DescribeQuorum returns INVALID_REQUEST if not handled by leader

Jason Gustafson created KAFKA-13940: --- Summary: DescribeQuorum returns INVALID_REQUEST if not handled by leader Key: KAFKA-13940 URL: https://issues.apache.org/jira/browse/KAFKA-13940 Project: Kafka

[Vote] KIP-787 - MM2 Interface to manage Kafka resources

Hi, I'd like to start a vote on KIP-787 https://cwiki.apache.org/confluence/display/KAFKA/KIP-787 %3A+MM2+Interface+to+manage+Kafka+resources Thanks Omnia

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #953

See Changes: -- [...truncated 478740 lines...] [2022-05-25T20:45:23.420Z] > Task :connect:api:publishToMavenLocal [2022-05-25T20:45:25.184Z] [2022-05-25T20:45:25.184Z] > Ta

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.0 #199

See Changes: -- [...truncated 285547 lines...] [2022-05-25T20:16:14.581Z] - Gradle detected a problem with the following location: '/home/jenkins/workspace/Kafka_kafka_3.0

[jira] [Created] (KAFKA-13939) Memory Leak When Logging Is Disabled In InMemoryTimeOrderedKeyValueBuffer

Jackson Newhouse created KAFKA-13939: Summary: Memory Leak When Logging Is Disabled In InMemoryTimeOrderedKeyValueBuffer Key: KAFKA-13939 URL: https://issues.apache.org/jira/browse/KAFKA-13939 Pro

[jira] [Resolved] (KAFKA-13937) StandardAuthorizer throws "ID 5t1jQ3zWSfeVLMYkN3uong not found in aclsById" exceptions into broker logs

[ https://issues.apache.org/jira/browse/KAFKA-13937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-13937. -- Fix Version/s: 3.3.0 Resolution: Duplicate I believe this is KAFKA-13649, which was fix

Re: [VOTE] KIP-833: Mark KRaft as Production Ready

Hi Ismael, Thanks for reviewing this. I removed the one-sentence comment in the KIP about "GA". I agree it's unrelated to the rest of the stuff discussed here, and potentially distracting. best, Colin On Wed, May 25, 2022, at 12:21, Ismael Juma wrote: > I'm +1 on this proposal with the inform

Re: [VOTE] KIP-833: Mark KRaft as Production Ready

In the list below, I accidentally included Luke Chen in the non-binding section. Actually, his vote belongs in the binding section. Sorry about that. best, Colin On Wed, May 25, 2022, at 11:42, Colin McCabe wrote: > Thanks, everyone! > > With binding +1 votes from: > Jason Gustafson > David Jac

[jira] [Resolved] (KAFKA-13909) Restart Kafka in KRaft mode with ACLs ends in a RuntimeException

[ https://issues.apache.org/jira/browse/KAFKA-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-13909. -- Fix Version/s: 3.3.0 Resolution: Duplicate > Restart Kafka in KRaft mode with ACLs ends

Re: [VOTE] KIP-833: Mark KRaft as Production Ready

I'm +1 on this proposal with the information we have today. We may have to adjust things depending on how things work out in practice (what lands when, user feedback, etc.). One nit: I'd remove the GA notation from the KIP as it's often associated with feature completeness and we are not aiming for

Re: [DISCUSS] KIP-827: Expose logdirs total and usable space via Kafka API

Hi, Mickael, Thanks for the KIP. Since this is mostly for monitoring and alerting, could we expose them as metrics instead of as part of the API? We already have a size metric per log. Perhaps we could extend that to add used/total metrics per disk? Thanks, Jun On Thu, May 19, 2022 at 10:21 PM

Re: [DISCUSS] KIP-831: Add metric for log recovery progress

Hi, Luke, Thanks for the KIP. Just one comment. 10. For kafka.log:type=LogManager,name=remainingLogsToRecovery, could we instead track the number of remaining segments? This monitors the progress at a finer granularity and is also consistent with the thread level metric. Thanks, Jun On Wed, Ma

Re: [VOTE] KIP-833: Mark KRaft as Production Ready

Thanks, everyone! With binding +1 votes from: Jason Gustafson David Jacot John Roesler José Armando García Sancio Bill Bejeck and non-binding +1 votes from: Israel Ekpo Luke Chen the vote passes. thanks, all. Colin On Tue, May 24, 2022, at 08:43, Bill Bejeck wrote: > Hi Colin, > > Thanks for

[jira] [Created] (KAFKA-13938) Jenkins builds are timing out after streams integration tests

David Arthur created KAFKA-13938: Summary: Jenkins builds are timing out after streams integration tests Key: KAFKA-13938 URL: https://issues.apache.org/jira/browse/KAFKA-13938 Project: Kafka

Re: [DISCUSS] KIP-844: Transactional State Stores

Also to dump my thoughts on the topic of "caching/flushing/transactions" that John raised, especially about their relations to range queries (I think some of them could be excluded from the scope of KIP-844, but I'd like to see if we have some consensus on the long-term vision): 0) Today all cache

Re: [VOTE] KIP-830: Allow disabling JMX Reporter

Thanks, +1 (binding). Ismael On Thu, May 19, 2022 at 5:04 AM Mickael Maison wrote: > Hi Ismael, > > That's a good idea, I've updated the KIP. > > Thanks, > Mickael > > On Tue, May 17, 2022 at 4:17 PM Federico Valeri > wrote: > > > > +1 (non binding) > > > > Thanks. > > > > On Tue, May 17, 2022

Re: [VOTE] KIP-830: Allow disabling JMX Reporter

Hi Mickael, Thanks for the KIP. +1 (binding). Kind regards, Tom On Thu, 19 May 2022 at 13:14, Mickael Maison wrote: > Hi Ismael, > > That's a good idea, I've updated the KIP. > > Thanks, > Mickael > > On Tue, May 17, 2022 at 4:17 PM Federico Valeri > wrote: > > > > +1 (non binding) > > > > T

Re: [VOTE] KIP-831: Add metric for log recovery progress

Hi Luke, Thanks for the KIP. +1 (binding). Kind regards, Tom On Fri, 20 May 2022 at 02:58, Raman Verma wrote: > ^^ (non binding) > > On Thu, May 19, 2022 at 5:40 PM Raman Verma wrote: > > > > Hello Luke, > > > > The proposal looks good to me. Thanks. +1 > > > > > > On Tue, May 17, 2022 at 9

Re: [VOTE] KIP-827: Expose logdirs total and usable space via Kafka API

Hi Mickael, Thanks for the KIP! +1 (binding). Kind regards, Tom On Thu, 19 May 2022 at 11:28, Federico Valeri wrote: > Thanks Mickael. > > +1 (non binding) > > On Wed, May 18, 2022 at 11:08 AM Divij Vaidya > wrote: > > > > +1 non binding. > > > > Divij Vaidya > > > > > > > > On Tue, May 17,

Re: [DISCUSS] KIP-831: Add metric for log recovery progress

Thanks Luke! LGTM. On Sun, 22 May 2022 at 05:18, Luke Chen wrote: > Hi Tom and Raman, > > Thanks for your comments. > > > 1. There's not a JIRA for this KIP (or the JIRA link needs updating). > 2. Similarly the link to this discussion thread needs updating. > > Please update the links to JIRA an

Re: [DISCUSS] KIP-845: HasField predicate for kafka connect

Hi Sagar, Added the examples to the KIP wiki as suggested. *---* *Thanks and Regards,* *Kumud Kumar Srivatsava Tirupati* On Wed, 25 May 2022 at 17:14, Sagar wrote: > Thanks for the KIP Kumud. > > Can you please add a couple of examples on how this would behave with > different combinations. I

Re: [DISCUSS] KIP-845: HasField predicate for kafka connect

Thanks for the KIP Kumud. Can you please add a couple of examples on how this would behave with different combinations. I think that way it would be easier to understand. Thanks! Sagar. On Wed, May 25, 2022 at 4:59 PM Kumud Kumar Srivatsava Tirupati < kumudkumartirup...@gmail.com> wrote: > Hi a

[DISCUSS] KIP-845: HasField predicate for kafka connect

Hi all, I have written a KIP for having a new HasField predicate for kafka connect transforms and would like to start a discussion. Please share your thoughts on the same. https://cwiki.apache.org/confluence/display/KAFKA/KIP-845%3A+%27HasField%27+predicate+for+kafka+connect *---* *Thanks and Reg

[jira] [Created] (KAFKA-13937) StandardAuthorizer throws "ID 5t1jQ3zWSfeVLMYkN3uong not found in aclsById" exceptions into broker logs

Jakub Scholz created KAFKA-13937: Summary: StandardAuthorizer throws "ID 5t1jQ3zWSfeVLMYkN3uong not found in aclsById" exceptions into broker logs Key: KAFKA-13937 URL: https://issues.apache.org/jira/browse/KAFKA-

Re: [DISCUSS] KIP-787 - MM2 Interface to manage Kafka resources

Hi everyone, If there's no major concern anymore, I'll start the voting process. On Fri, May 20, 2022 at 5:58 PM Omnia Ibrahim wrote: > Hi Colin, > > >Thanks for the clarification. I agree it's reasonable for people to want > to use their own implementations of Admin. And we could have a config

[jira] [Created] (KAFKA-13936) Invalid consumer lag when monitoring from a kafka streams application

Prashanth Joseph Babu created KAFKA-13936: - Summary: Invalid consumer lag when monitoring from a kafka streams application Key: KAFKA-13936 URL: https://issues.apache.org/jira/browse/KAFKA-13936