Re: Contribution req

Hi Elxan, Done. Thanks for the interest in Apache Kafka. Luke On Mon, Jun 20, 2022 at 12:25 AM Elxan Eminov wrote: > Hi, > I'd like to request permissions to contribute to Apache Kafka, > my wiki and jira ID's are "elkkhan" > > Thanks! >

[jira] [Resolved] (KAFKA-13483) Stale Missing ISR on a partition after a zookeeper timeout

[ https://issues.apache.org/jira/browse/KAFKA-13483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13483. --- Fix Version/s: 3.1.0 Resolution: Fixed > Stale Missing ISR on a partition after a zookee

[jira] [Resolved] (KAFKA-13720) Few topic partitions remain under replicated after broker lose connectivity to zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-13720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13720. --- Fix Version/s: 3.1.0 Resolution: Fixed > Few topic partitions remain under replicated af

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

1 from me. > > Jun > > On Mon, Jun 13, 2022 at 8:04 AM Mickael Maison > wrote: > > > +1 (binding) > > > > Thanks for the KIP! > > > > Mickael > > > > On Sun, Jun 12, 2022 at 5:26 PM Yu Kvicii wrote: > > > > > >

[jira] [Created] (KAFKA-13981) metadata shell doesn't recognize some new record types

Luke Chen created KAFKA-13981: - Summary: metadata shell doesn't recognize some new record types Key: KAFKA-13981 URL: https://issues.apache.org/jira/browse/KAFKA-13981 Project: Kafka Issue Type

[jira] [Resolved] (KAFKA-13891) sync group failed with rebalanceInProgress error cause rebalance many rounds in coopeartive

[ https://issues.apache.org/jira/browse/KAFKA-13891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13891. --- Fix Version/s: 3.3.0 Resolution: Fixed > sync group failed with rebalanceInProgress er

[jira] [Resolved] (KAFKA-13917) Avoid calling lookupCoordinator() in tight loop

[ https://issues.apache.org/jira/browse/KAFKA-13917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13917. --- Fix Version/s: 3.3.0 Resolution: Fixed > Avoid calling lookupCoordinator() in tight l

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

t; > > The proposal looks good to me. Thanks. +1 > > > > > > > > > On Tue, May 17, 2022 at 9:26 PM James Cheng > > wrote: > > > > > > > > +1 (non-binding) > > > > > > > > -James > > > > > > &g

Re: [VOTE] KIP-840: Config file option for MessageReader/MessageFormatter in ConsoleProducer/ConsoleConsumer

Hi Alexandre, +1 (binding) from me. Thank you. Luke On Thu, Jun 9, 2022 at 10:24 AM John Roesler wrote: > Thanks for the KIP, Alexandre! > > I’m +1 (binding) > > -John > > On Wed, Jun 8, 2022, at 20:54, deng ziming wrote: > > Thank you for this KIP, > > > > +1 (non-binding) > > > > -- > >

Re: [DISCUSS] KIP-840: Config file option for MessageReader/MessageFormatter in ConsoleProducer/ConsoleConsumer

o the KIP? >> > This was covered by the sentence "As for > --producer-property/--consumer-property with > --consumer.config/--producer.config, any value from option --property would > override value from config file." > I did add an example for this situation. > >

Re: [DISCUSS] KIP-840: Config file option for MessageReader/MessageFormatter in ConsoleProducer/ConsoleConsumer

Hi Alexandre, Thanks for the KIP. Some comments: 1. Usually, in "Proposed Changes" section, we won't put PR link there. Maybe you can take KIP-824 as a reference. 2.

Re: Upgrade log4j to log4j2

Hi Nicola, Here's the plan for log4j and log4j2 in Kafka project: - adopt reload4j in Kafka 3.2.0 - switch to log4j2 to Kafka 4.0.0 Thank you. Luke On Tue, Jun 7, 2022 at 11:18 PM Nozza, Nicola wrote: > Hi, > > I'm contacting you to please ask for an ETA, if it is planned, for the > release

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

Hi Mickael, Thanks for the KIP. It's a good improvement. Although it's a little weird that we introduce a "new deprecated" config, it seems like this is the best solution we can have now. +1 (binding) from me. Thank you. Luke On Thu, May 26, 2022 at 12:21 AM Ismael Juma wrote: > Thanks, +1

[jira] [Resolved] (KAFKA-13933) Stuck SSL/TLS unit tests in case of authentication failure

[ https://issues.apache.org/jira/browse/KAFKA-13933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13933. --- Fix Version/s: 3.3.0 Resolution: Fixed > Stuck SSL/TLS unit tests in case of authenticat

Re: [DISCUSS] KIP-846: Task-level Streams metrics for bytes/records Produced

Hi Sophie, Sorry for the late comments. Thanks for the KIP. One question from me: In test plan section, you mentioned we'll have benchmark for potential performance regression. And in the end, you said: See #2 under Rejected Alternatives for more on this. But I didn't find there's #2 in

Re: Re-run Jenkins build

Hi José, I think you should have the same permissions as I have, and I can login jenkins. Anyway, I can help you re-run the jenkins build. Just point me the jenkins build link. Or you can actually merge with the latest trunk to trigger the build. Thank you. Luke On Sat, Jun 4, 2022 at 5:52 AM

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

the > remaining segments for the current log assigned to a thread. Also, would it > be better to use ToRecover instead of ToRecovery? > > Thanks, > > Jun > > On Fri, Jun 3, 2022 at 1:18 AM Luke Chen wrote: > > > Hi Jun, > > > > > how do we implement kafka.log &

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

he segment level? > > Jun > > On Thu, Jun 2, 2022 at 3:39 AM Luke Chen wrote: > > > Hi Jun, > > > > Thanks for the comment. > > > > Yes, I've tried to work on this way to track the number of remaining > > segments, but it will change the design

[jira] [Resolved] (KAFKA-13718) kafka-topics describe topic with default config will show `segment.bytes` overridden config

[ https://issues.apache.org/jira/browse/KAFKA-13718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13718. --- Fix Version/s: 3.3.0 Resolution: Fixed > kafka-topics describe topic with default con

[jira] [Created] (KAFKA-13955) Fix failing KRaftClusterTest tests

Luke Chen created KAFKA-13955: - Summary: Fix failing KRaftClusterTest tests Key: KAFKA-13955 URL: https://issues.apache.org/jira/browse/KAFKA-13955 Project: Kafka Issue Type: Test

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

gt; > 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). >

Re: [DISCUSS] KIP-843 Adding metricOrElseCreate method to Metrics.

KIP doesn't throw any > exceptions. Also, the KIP was an afterthought, which came up during the PR > review of this: https://github.com/apache/kafka/pull/12121 > > Let me know if that's ok. > > Thanks! > Sagar. > > On Tue, May 31, 2022 at 8:40 AM Luke Chen wrote: >

Re: [DISCUSS] KIP-843 Adding metricOrElseCreate method to Metrics.

Hi Sagar, Thanks for the KIP. In the `Compatibility` section, you mentioned: *The changes are backward compatible and needs no deprecation/migration.* But as you said, we won't throw `IllegalArgumentException` in `addMetric` method. Isn't that the compatibility issue that should be put in

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

+1 from me. Kraft is coming!!! Luke On Tue, May 24, 2022 at 7:26 AM Israel Ekpo wrote: > +1 (non-binding) from me. > > I am very happy to finally see this. > > On Mon, May 23, 2022 at 6:08 PM Jason Gustafson > > wrote: > > > Thanks Colin. +1 from me. Very exciting! > > > > On Tue, May 17,

Re: Re: Fw: Re: how to apply to create a KIP

/3d5o7h17ztjztjhblx4fln0wbbs1rmdq Thank you. Luke On Mon, May 23, 2022 at 4:30 PM 胡德祺 <16120...@bjtu.edu.cn> wrote: > Hi, Luke Chen. Thanks. > I have created and published the KIP： > https://cwiki.apache.org/confluence/display/KAFKA/KIP-842%3A+Add+richer+group+offset+reset+mechanisms >

Re: Requesting permissions to contribute to Kafka

Hi, Done. Thank you. Luke On Mon, May 23, 2022 at 1:40 PM Kumud Kumar Srivatsava Tirupati < kumudkumartirup...@gmail.com> wrote: > Hi team, > I am planning to work on https://issues.apache.org/jira/browse/KAFKA-13926 > and wanted to create a KIP for the same. Requesting permissions on the >

Re: Fw: Re: how to apply to create a KIP

HI 德祺, I've granted your permission. You are able to create KIP now. Thanks for the interest in Apache Kafka. Luke On Mon, May 23, 2022 at 9:51 AM 胡德祺 <16120...@bjtu.edu.cn> wrote: > hi, I want to apply to create a KIP. My wiki ID is "hudeqi". Please help > me add it in. > > > -原始邮件- >

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

> > rather than describing the tree you'd see in an MBean console. > > > > Kind regards, > > > > Tom > > > > On Wed, 11 May 2022 at 09:08, Luke Chen wrote: > > > > > > And if people start using RemainingLogs and RemainingSegments and >

[jira] [Created] (KAFKA-13919) Add metric for log recovery progress

Luke Chen created KAFKA-13919: - Summary: Add metric for log recovery progress Key: KAFKA-13919 URL: https://issues.apache.org/jira/browse/KAFKA-13919 Project: Kafka Issue Type: New Feature

Re: Kafka 2.7.0 vulnerabilities

Hi Udit, If v3.0.0 is vulnerable to this CVE, then I believe v2.7.0 is also vulnerable, since the component used in v2.7.0 must be in the older version. Please upgrade to v3.1.1 or later. Thank you. Luke On Thu, May 19, 2022 at 6:41 PM Seth, Udit wrote: > Greetings Concerned, > Currently,

Re: [VOTE] KIP-836: Addition of Information in DescribeQuorumResponse about Voter Lag

Hi Niket, Thanks for the KIP! +1 (binding) from me. Luke On Thu, May 19, 2022 at 8:27 AM deng ziming wrote: > +1(non-binding) > > Thanks for this KIP. > -- > Best, > Ziming > > > On May 17, 2022, at 1:14 AM, Niket Goel > wrote: > > > > Hi all, > > > > I would like to start a vote for

Re: [VOTE] KIP-835: Monitor KRaft Controller Quorum Health

Hi José, Thanks for the KIP! +1 (binding) from me. Luke On Thu, May 19, 2022 at 2:05 AM José Armando García Sancio wrote: > Hi Guozhang, thanks for the feedback. > > > Guozhang wrote: > > Could you elaborate a bit on what does "load-processing-time-us" > measure? I > > looked through the

Re: [ANNOUNCE] Apache Kafka 3.2.0

t; Bruno Cadonna, Chang, Chia-Ping Tsai, Chris Egerton, Colin P. Mccabe, > > > Colin Patrick McCabe, Cong Ding, David Arthur, David Jacot, David Mao, > > > defhacks, dengziming, Ed B, Edwin, florin-akermann, GauthamM-official, > > > GuoPhilipse, Guozhang Wang, Hao Li, Haoze

Re: Permission request to contribute

Thanks Bill! @Austin, your wiki permission is set now. Thank you. Luke On Wed, May 18, 2022 at 6:40 AM Bill Bejeck wrote: > Hi Austin, > > You're all set with Jira, but at the moment it seems like there's a > connection issue with the wiki and I haven't been able to add you there > yet. >

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

Hi Mickael, +1 (binding) from me. Thanks for the KIP! Luke On Tue, May 17, 2022 at 9:30 PM Mickael Maison wrote: > Hi, > > I'd like to start a vote on KIP-827. It proposes exposing the total > and usable space of logdirs > via the DescribeLogDirs API: > >

[jira] [Created] (KAFKA-13908) RuntimeException will be thrown in BrokerServer.startup, not the cause of exception

Luke Chen created KAFKA-13908: - Summary: RuntimeException will be thrown in BrokerServer.startup, not the cause of exception Key: KAFKA-13908 URL: https://issues.apache.org/jira/browse/KAFKA-13908

[jira] [Resolved] (KAFKA-13905) Fix failing ServerShutdownTest.testCleanShutdownAfterFailedStartupDueToCorruptLogs

[ https://issues.apache.org/jira/browse/KAFKA-13905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13905. --- Fix Version/s: 3.3.0 Resolution: Fixed > Fix fail

Re: CI on Kafka seems to be failing even on trunk branch

Thanks for Divij's answer. One thing I'd like to add is that it'd be better if you can help investigate and fix those flaky tests. :) Thank you. Luke On Tue, May 17, 2022 at 4:14 AM Divij Vaidya wrote: > Hi Lim > > We have quite a few tests which are flaky and fail stochastically from time >

Re: [ANNOUNCE] Apache Kafka 3.1.1

hat transform or react > >> to the streams of data. > >> > >> > >> Apache Kafka is in use at large and small companies worldwide, including > >> Capital One, Goldman Sachs, ING, LinkedIn, Netflix, Pinterest, Rabobank, > >> Target, The New York T

[jira] [Created] (KAFKA-13905) Fix failing ServerShutdownTest.testCleanShutdownAfterFailedStartupDueToCorruptLogs

Luke Chen created KAFKA-13905: - Summary: Fix failing ServerShutdownTest.testCleanShutdownAfterFailedStartupDueToCorruptLogs Key: KAFKA-13905 URL: https://issues.apache.org/jira/browse/KAFKA-13905 Project

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

Hi all, I'd like to start a vote on KIP to expose metrics for log recovery progress. These metrics would let the admins have a way to monitor the log recovery progress. Details can be found here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-831%3A+Add+metric+for+log+recovery+progress

Re: Contributor Permission

Hi Jack, I've added you into the contribution list. Thanks for the interest in Apache Kafka. Luke On Thu, May 12, 2022 at 8:44 AM Jack Burgoyne wrote: > Hello, > > I'd like to start contributing to Kafka, could I have contributor > permission for my Jira username: jcbu2718? > > Thank you, >

Re: Request to be added to Kafka Jira project

Hi Lim, I've added you into the contribution list in JIRA. Thanks for the interest in Apache Kafka. Luke On Thu, May 12, 2022 at 2:09 PM Lim Qingwei wrote: > Sorry, I misread, my jira id is qingwei91 > > On Thu, May 12, 2022 at 7:01 AM Lim Qingwei wrote: > > > Hi, I am looking to pick this

Re: [VOTE] KIP-834: Pause / Resume KafkaStreams Topologies

Hi Jim, I'm +1. (please add some note in KIP about the stream resetting tool can't be used in paused state) Thanks for the KIP! Luke On Wed, May 11, 2022 at 9:09 AM Guozhang Wang wrote: > Thanks Jim. +1 from me. > > On Tue, May 10, 2022 at 4:51 PM Matthias J. Sax wrote: > > > I had one minor

Re: [DISCUSS] KIP-834: Pause / Resume KafkaStreams Topologies

as the members and the tool will be > simultaneously trying to set the committed offsets to different values, etc. > > Jim, can you also make it a point to document this? As Luke points out, it > might be a natural thing to want to do. > > Thanks, > John > > On Wed, May 11, 2022,

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

. And if people start using > RemainingLogs and RemainingSegments and then REALLY FEEL like they need > RemainingBytes, then we can always add it in the future. > > Thanks Luke, for the detailed explanation, and for responding to my > feedback! > > -James > > Sent from my iPho

Re: [HEADS-UP] Modification to KIP Template

Hi Mickael, +1 to add "test plan" section to KIP template. Thanks for the improvement! Luke On Tue, May 10, 2022 at 11:21 PM Mickael Maison wrote: > Hi, > > I did not see any comments nor concerns so I went ahead and added the > Test Plan section to the KIP template. > > Thanks, > Mickael > >

Re: [DISCUSS] KIP-834: Pause / Resume KafkaStreams Topologies

Hi Jim, Thanks for the KIP. Overall LGTM! One late question: Could we run the stream resetter tool (i.e. kafka-streams-application-reset.sh) during pause state? I can imagine there's a use case that after pausing for a while, user just want to continue with the latest offset, and skipping the

Re: [DISCUSS] KIP-835: Monitor KRaft Controller Quorum Health

Hi José, Thanks for the KIP! Some questions: 1. Jason has asked but you didn't answer: What is the default value for ` metadata.monitor.write.interval.ms`? 2. The `noopRecord` API key is `TBD`. Why can't we put the "currently used API Key nums + 1" into it? Any concern? 3. typo:

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

this week. Thank you. Luke On Fri, May 6, 2022 at 6:00 PM Luke Chen wrote: > Hi James, > > Thanks for your input. > > For the `RemainingBytesToRecovery` metric proposal, I think there's one > thing I didn't make it clear. > Currently, when log manager start up, we'll try to load

Re: Permission to contribute

Hi Tom, You're all done. Thanks for joining us! :) Luke On Mon, May 9, 2022 at 4:47 PM Thomas Cooper wrote: > Hi, > > I would like to contribute to the project. My usernames are: > > wiki: tomncooper > jira: tomncooper > > If someone could approve access for me I would be grateful. > >

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

5 partitions, then it would make sense that > each thread has its own counter. > If the threads works on a single pool of 10 partitions, then it would > probably mean that the counter is on the pool of partitions itself, and not > on each thread. > > -James > > > On May

Re: The latest version of Kafka 3.1.0 does not support Ubuntu 14 04？ The Java client cannot send a message

Hi zw, I think Kafka should be able to run under any Linux environment. Could you share the client/broker logs for troubleshooting? Thank you. Luke On Thu, May 5, 2022 at 10:13 PM zw wrote: > Hello! My English is not very good, please forgive me. > The questions are as follows： > Install

Re: There is the mistake on kafka.apache.org

Hi Emily, Thanks for reporting the issue. But the doc you referred to is for Kafka v0.8. This issue has been fixed in later versions (PR: https://github.com/apache/kafka/pull/2010) So, you can just check the latest version of documentation. Of course, if you're interested, welcome to submit a PR

Re: [VOTE] 3.1.1 RC1

Hi Tom, I did: 1. check the signature and checksums 2. ran quick start with java17 + sacla2.12 3. browse java docs/documentations +1 (non-binding) Thanks for running the release. Luke On Thu, May 5, 2022 at 12:43 AM Bill Bejeck wrote: > Hi Tom, > > Thanks for running the release! > > I did

Re: [VOTE] 3.2.0 RC1

Hi Bruno, I did: 1. check the signature and checksums 2. ran quick start with java17 + sacla2.12 3. browse java docs/documentations +1 (non-binding) Thanks for running the release. Luke On Thu, May 5, 2022 at 1:23 AM Mickael Maison wrote: > Hi Bruno, > > I checked signatures and checksums,

[jira] [Created] (KAFKA-13875) update docs to include topoicId for kafka-topics.sh --describe output

Luke Chen created KAFKA-13875: - Summary: update docs to include topoicId for kafka-topics.sh --describe output Key: KAFKA-13875 URL: https://issues.apache.org/jira/browse/KAFKA-13875 Project: Kafka

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

Hi devs, If there are no other comments, I'll start a vote tomorrow. Thank you. Luke On Sun, May 1, 2022 at 5:08 PM Luke Chen wrote: > Hi James, > > Sorry for the late reply. > > Yes, this is a good point, to know how many segments to be recovered if > there are some large

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

Hi Colin, So exciting to see the KIP to mark the Kraft production ready! Just one comment: We should make sure the period between ZK deprecation (i.e. v3.4.0) to ZK removal (i.e. v4.0.0) is not too short. Do we have any expectation for the deprecation period? After all, this is not a small

Re: Possible Bug: kafka-reassign-partitions causing the data retention time to be reset

Hi Fared, > So I guess the process applying the retention policy (log cleaner?) uses that timestamp to check whether the segment file should be deleted or not. So I ended up with a lot more data than we were supposed to store, since we are basically doubling the retention time of all the freshly

[jira] [Resolved] (KAFKA-13865) Fix ResponseSendTimeMs metric in RequestChannel.scala was removed repeatedly

[ https://issues.apache.org/jira/browse/KAFKA-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13865. --- Fix Version/s: 3.3.0 Resolution: Fixed > Fix ResponseSendTimeMs met

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

flect partition size? Could it be > RemainingSegmentsToRecover? Or even RemainingBytesToRecover? > > -James > > Sent from my iPhone > > > On Apr 20, 2022, at 2:01 AM, Luke Chen wrote: > > > > Hi all, > > > > I'd like to propose a KIP to expose a metric

[jira] [Resolved] (KAFKA-12380) Executor in Connect's Worker is not shut down when the worker is

[ https://issues.apache.org/jira/browse/KAFKA-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-12380. --- Fix Version/s: 3.3.0 Resolution: Fixed > Executor in Connect's Worker is not shut down w

Re: [kafka-clients] Re: [VOTE] 3.2.0 RC0

Hi Bruno, I think this PR might also need to be included in next release candidate because it's a bug fix/optimization for an issue introduced in v3.2.0. https://github.com/apache/kafka/pull/12096 cc Ismael Thank you. Luke On Thu, Apr 28, 2022 at 3:36 AM Guozhang Wang wrote: > Hi Bruno, > >

Re: [VOTE] 3.1.1 RC0

Juma wrote: > > I added a comment to that PR. Let's figure out if we need an additional > > change before doing the next RC. > > > > Ismael > > > > On Tue, Apr 12, 2022 at 7:47 PM Luke Chen wrote: > > > > > Thanks for pointing that out, David. > >

Re: Request permission to contribute to Kafka KIP

Hi Hongwei, Done. Thanks for the interest in Apache Kafka. Luke On Sun, Apr 24, 2022 at 11:08 PM Hongtenzone John wrote: > Hi Kafka team, > I'd like to request permission to contribute to Kafka to propose a KIP. > Wiki ID: hongwei.xiangJira ID: hongwei.xiang > Thanks.Best Regards,Hongwei

Re: [DISCUSS] KIP-829: (console-consumer) add print.topic property

e ordering of the message printed, there is no intention to > console-consumer on this topic. > > On Sun, Apr 24, 2022, 16:12 Luke Chen wrote: > > > +1 for printing anything we got without ordering. > > I can imagine the ordering of the random topics records will be > complicated > > a

Re: [DISCUSS] KIP-829: (console-consumer) add print.topic property

arding this. > > Thank you, > > Evans > > > On Wed, Apr 20, 2022 at 1:59 PM Luke Chen wrote: > > > Hi Evans, > > > > This is a good feature that we missed before. > > +1 to add an example. > > I saw your WIP PR already added it, please put

[jira] [Resolved] (KAFKA-13852) Kafka Acl documentation bug for wildcard '*'

[ https://issues.apache.org/jira/browse/KAFKA-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13852. --- Fix Version/s: 3.3.0 Resolution: Fixed > Kafka Acl documentation bug for wildc

[jira] [Resolved] (KAFKA-13834) batch drain for nodes might have starving issue

[ https://issues.apache.org/jira/browse/KAFKA-13834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13834. --- Fix Version/s: 3.3.0 Resolution: Fixed > batch drain for nodes might have starving is

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

Hi all, I'd like to propose a KIP to expose a metric for log recovery progress. This metric would let the admins have a way to monitor the log recovery progress. Details can be found here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-831%3A+Add+metric+for+log+recovery+progress Any

Re: [DISCUSS] KIP-829: (console-consumer) add print.topic property

Hi Evans, This is a good feature that we missed before. +1 to add an example. I saw your WIP PR already added it, please put them into the KIP. Thank you. Luke On Sat, Apr 16, 2022 at 7:39 AM John Roesler wrote: > Hi Evans, > > Thanks for the KIP! > > I agree with Mickael; it would be good to

[jira] [Resolved] (KAFKA-13832) Flaky test TopicCommandIntegrationTest.testAlterAssignment

[ https://issues.apache.org/jira/browse/KAFKA-13832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13832. --- Fix Version/s: 3.3.0 Assignee: dengziming Resolution: Fixed > Flaky t

[jira] [Resolved] (KAFKA-13737) Flaky kafka.admin.LeaderElectionCommandTest.testPreferredReplicaElection

[ https://issues.apache.org/jira/browse/KAFKA-13737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13737. --- Resolution: Fixed Resolved with PR: https://github.com/apache/kafka/pull/11681 > Fl

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

Hi Mickael, Thanks for the KIP! This is a good improvement. (3) +1 for not adding the number of files in the directory. Counting the file numbers should be slow. (7) Could you make the fields clear in `DescribeLogDirsResponse`, to mention the returned number is size in Byte (or not?) Thank you.

[jira] [Resolved] (KAFKA-13653) Proactively discover alive brokers from bootstrap server lists when all nodes are down

[ https://issues.apache.org/jira/browse/KAFKA-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13653. --- Resolution: Duplicate > Proactively discover alive brokers from bootstrap server lists when

Re: maxParallelForks while running tests

Hi Unmesh, Are you running into any issue with that? So far, the `maxParallelForks` can be set via gradle argument: https://github.com/apache/kafka/blob/trunk/build.gradle#L78 And in Jenkins, it looks like we default to 2. https://github.com/apache/kafka/blob/trunk/Jenkinsfile#L40 Thank you.

Re: [VOTE] 3.1.1 RC0

Thanks for pointing that out, David. +1 to include this PR since we've already included the first fix for KAFKA-13794, and this is a follow up fix for it. Thank you. Luke On Wed, Apr 13, 2022 at 2:31 AM David Jacot wrote: > Hi Tom, > > Thanks for running the release. I wonder if we should

[jira] [Resolved] (KAFKA-13802) Uncaught exception in scheduled task 'flush-log' (kafka.utils.KafkaScheduler)

[ https://issues.apache.org/jira/browse/KAFKA-13802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13802. --- Resolution: Fixed Fixed in [#11605|https://github.com/apache/kafka/pull/11605]  > Uncau

[jira] [Resolved] (KAFKA-13792) Wrong package name in Scala test files

[ https://issues.apache.org/jira/browse/KAFKA-13792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13792. --- Resolution: Not A Problem > Wrong package name in Scala test fi

Re: Requesting permission for JIRA/Wiki

Hi Divij, Done. Thanks for the interest in Apache Kafka. Thank you. Luke On Sat, Apr 9, 2022 at 6:28 AM Divij Vaidya wrote: > Correction: I would like to open a PR for > https://issues.apache.org/jira/browse/KAFKA-12319 and not > https://issues.apache.org/jira/browse/KAFKA-13530 as stated

[jira] [Created] (KAFKA-13804) Log broker shutdown reason at the end of log output

Luke Chen created KAFKA-13804: - Summary: Log broker shutdown reason at the end of log output Key: KAFKA-13804 URL: https://issues.apache.org/jira/browse/KAFKA-13804 Project: Kafka Issue Type

[jira] [Resolved] (KAFKA-13791) Fix FetchResponse#`fetchData` and `forgottenTopics`: Assignment of lazy-initialized members should be the last step with double-checked locking

[ https://issues.apache.org/jira/browse/KAFKA-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13791. --- Fix Version/s: 3.3.0 Resolution: Fixed > Fix FetchResponse#`fetchData` and `forgottenTop

Re: HACKING vulnerability is SpringBoot (Java) for apache kafka

Hi, The impact for the CVE-2022-22965? Since this is a RCE vulnerability, which means the whole system (including Kafka and ZK) is under the attackers' control, and can do whatever they want. The ideal fix for this is to upgrade Spring Framework 5.3.18 and 5.2.20 or greater. Alternatively, you

[jira] [Resolved] (KAFKA-13777) Fix FetchResponse#responseData: Assignment of lazy-initialized members should be the last step with double-checked locking

[ https://issues.apache.org/jira/browse/KAFKA-13777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13777. --- Resolution: Fixed > Fix FetchResponse#responseData: Assignment of lazy-initialized members sho

Re: [DISCUSS] KIP-660: Pluggable ReplicaPlacer

ow this? Given the information passed to the method, > > > seems like this could only be thrown if there were obviously invalid > > > arguments, like a negative number or zero. Can we just guarantee such > > > invalid arguments aren't passed in? > > > > >

Re: [DISCUSS] KIP-660: Pluggable ReplicaPlacer

Hi Mickael, Thanks for the KIP! It's indeed a pain point for the Kafka admins. I have some comments: 1. Typo in motivation section: When administrators [when to] remove brokers from a cluster, 2. If different `replica.placer.class.name` configs are set in all controllers, I think only the

Re: Potential bugs in resizing kafka thread

Hi Feiyan, It did look like a bug. Could you open a bug in JIRA here ? One thing I don't fully understand from the unit test is that, you have output "error distributions: $tpsWithoutResize". I thought the bug

Re: [VOTE] KIP-824 Allowing dumping segmentlogs limiting the batches in the output

Hi Sergio, Thanks for the KIP! +1(binding) from me. Thank you. Luke On Fri, Mar 25, 2022 at 1:40 PM Sergio Daniel Troiano wrote: > Hi lads, > > I would like to start the vote on this: > >

Re: [DISCUSS] KIP-824 Allowing dumping segmentlogs limiting the batches in the output

ing it in terms of number of batches? I think it's a > >> bit more user friendly than a size in raw bytes. > >> For example: --num-batches: The number of batches to read from the log > segment. > >> > >> Thanks, > >> Mickael > >> > >>

Re: [DISCUSS] Apache Kafka 3.2.0 release

Added the jira query link for the blocker tickets that needed to help.

[jira] [Resolved] (KAFKA-13672) Race condition in DynamicBrokerConfig

[ https://issues.apache.org/jira/browse/KAFKA-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13672. --- Fix Version/s: 3.3.0 Resolution: Fixed > Race condition in DynamicBrokerCon

Re: [VOTE] KIP-794: Strictly Uniform Sticky Partitioner

Hi Artem, Thanks for the KIP and the patience during discussion! +1 binding from me. Luke On Thu, Mar 24, 2022 at 3:43 AM Ismael Juma wrote: > Thanks for the KIP and for taking the time to address all the feedback. +1 > (binding) > > Ismael > > On Mon, Mar 21, 2022 at 4:52 PM Artem Livshits >

Re: [VOTE] KIP-653: Upgrade log4j to log4j2

Hi Dongjin, I know there are some discussions about the compatibility issue. Could you help answer this question? Thank you. Luke On Fri, Mar 18, 2022 at 3:32 AM Ismael Juma wrote: > Hi all, > > The KIP compatibility section does not include enough detail. I am puzzled > how we voted +1 given

[jira] [Resolved] (KAFKA-7077) KIP-318: Make Kafka Connect Source idempotent

[ https://issues.apache.org/jira/browse/KAFKA-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-7077. -- Resolution: Fixed > KIP-318: Make Kafka Connect Source idempot

[jira] [Created] (KAFKA-13747) refactor TopologyTest to test different store type with parametrized

Luke Chen created KAFKA-13747: - Summary: refactor TopologyTest to test different store type with parametrized Key: KAFKA-13747 URL: https://issues.apache.org/jira/browse/KAFKA-13747 Project: Kafka

Re: Granting permission for Create KIP

Hi JiaJun You're all set now. Thanks for your interest in Apache Kafka. Luke On Sun, Mar 13, 2022 at 12:59 PM jiajun0918 wrote: > Please grant permission for Create KIP to wiki ID: wjiajun

[jira] [Resolved] (KAFKA-13717) KafkaConsumer.close throws authorization exception even when commit offsets is empty

[ https://issues.apache.org/jira/browse/KAFKA-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13717. --- Fix Version/s: 3.2.0 Assignee: Vincent Jiang Resolution: Fixed

Re: [VOTE] 3.0.1 RC0

Hi Mickael, Thanks for running the release! I did the following: 1. Validated the scala 2.13 checksums 2. Spot checked the java docs 3. Ran the quick start with scala 2.13 (found a minor bug KAFKA-13718 , won't block the release) +1

[jira] [Created] (KAFKA-13718) kafka-topics create with default config will show `segment.bytes` overridden config

Luke Chen created KAFKA-13718: - Summary: kafka-topics create with default config will show `segment.bytes` overridden config Key: KAFKA-13718 URL: https://issues.apache.org/jira/browse/KAFKA-13718

<    1   2   3   4   5   6   7   8   9   10   >