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

[James Cheng]

+1 (non-binding)

-James

Sent from my iPhone

> On May 16, 2022, at 12:12 AM, Luke Chen  wrote:
> 
> 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
> 
> Any feedback is appreciated.
> 
> Thank you.
> Luke

Re: [ANNOUNCE] Apache Kafka 3.2.0

[Sagar]

Thanks Bruno!

Sagar.

On Wed, May 18, 2022 at 8:27 AM Luke Chen  wrote:

> Thank you, Bruno!
>
> On Wed, May 18, 2022 at 2:16 AM Guozhang Wang  wrote:
>
> > Congrats to everyone who's contributed to 3.2.0, and special thank you to
> > Bruno for running the release!
> >
> > Guozhang
> >
> > On Tue, May 17, 2022 at 9:52 AM Bill Bejeck  wrote:
> >
> > > Thanks for running the release Bruno!
> > >
> > > On Tue, May 17, 2022 at 12:02 PM Bruno Cadonna 
> > wrote:
> > >
> > > > The Apache Kafka community is pleased to announce the release for
> > Apache
> > > > Kafka 3.2.0
> > > >
> > > > * log4j 1.x is replaced with reload4j (KAFKA-9366)
> > > > * StandardAuthorizer for KRaft (KIP-801)
> > > > * Send a hint to the partition leader to recover the partition
> > (KIP-704)
> > > > * Top-level error code field in DescribeLogDirsResponse (KIP-784)
> > > > * kafka-console-producer writes headers and null values (KIP-798 and
> > > > KIP-810)
> > > > * JoinGroupRequest and LeaveGroupRequest have a reason attached
> > (KIP-800)
> > > > * Static membership protocol lets the leader skip assignment
> (KIP-814)
> > > > * Rack-aware standby task assignment in Kafka Streams (KIP-708)
> > > > * Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
> > > > * Connect APIs list all connector plugins and retrieve their
> > > > configuration (KIP-769)
> > > > * TimestampConverter SMT supports different unix time precisions
> > > (KIP-808)
> > > > * Connect source tasks handle producer exceptions (KIP-779)
> > > >
> > > > All of the changes in this release can be found in the release notes:
> > > > https://www.apache.org/dist/kafka/3.2.0/RELEASE_NOTES.html
> > > >
> > > >
> > > > You can download the source and binary release (Scala 2.12 and 2.13)
> > > from:
> > > > https://kafka.apache.org/downloads#3.2.0
> > > >
> > > >
> > > >
> > >
> >
> ---
> > > >
> > > >
> > > > Apache Kafka is a distributed streaming platform with four core APIs:
> > > >
> > > >
> > > > ** The Producer API allows an application to publish a stream of
> > records
> > > to
> > > > one or more Kafka topics.
> > > >
> > > > ** The Consumer API allows an application to subscribe to one or more
> > > > topics and process the stream of records produced to them.
> > > >
> > > > ** The Streams API allows an application to act as a stream
> processor,
> > > > consuming an input stream from one or more topics and producing an
> > > > output stream to one or more output topics, effectively transforming
> > the
> > > > input streams to output streams.
> > > >
> > > > ** The Connector API allows building and running reusable producers
> or
> > > > consumers that connect Kafka topics to existing applications or data
> > > > systems. For example, a connector to a relational database might
> > > > capture every change to a table.
> > > >
> > > >
> > > > With these APIs, Kafka can be used for two broad classes of
> > application:
> > > >
> > > > ** Building real-time streaming data pipelines that reliably get data
> > > > between systems or applications.
> > > >
> > > > ** Building real-time streaming applications that 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 Times, Uber, Yelp, and Zalando, among others.
> > > >
> > > > A big thank you for the following 113 contributors to this release!
> > > >
> > > > A. Sophie Blee-Goldman, Adam Kotwasinski, Aleksandr Sorokoumov,
> > > > Alexandre Garnier, Alok Nikhil, aSemy, Bounkong Khamphousone,
> bozhao12,
> > > > 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 Wu, Idan Kamara, Ismael
> Juma,
> > > > Jason Gustafson, Jason Koch, Jeff Kim, jiangyuan, Joel Hamill, John
> > > > Roesler, Jonathan Albrecht, Jorge Esteban Quilcate Otoya, Josep Prat,
> > > > Joseph (Ting-Chou) Lin, José Armando García Sancio, Jules Ivanic,
> > Julien
> > > > Chanaud, Justin Lee, Justine Olshan, Kamal Chandraprakash, Kate
> > Stanley,
> > > > keashem, Kirk True, Knowles Atchison, Jr, Konstantine Karantasis,
> > > > Kowshik Prakasam, kurtostfeld, Kvicii, Lee Dongjin, Levani
> Kokhreidze,
> > > > lhunyady, Liam Clarke-Hutchinson, liym, loboya~, Lucas Bradstreet,
> > > > Ludovic DEHON, Luizfrf3, Luke Chen, Marc Löhe, Matthew Wong, Matthias
> > J.
> > > > Sax, Michal T, Mickael Maison, Mike Lothian, mkandaswamy, Márton
> > > > Sigmond, Nick Telford, Niket, Okada Haruki, Paolo Patierno, Patrick
> > > > Stuedi, Philip Nee, Prateek Agarwal, prince-mahajan, Rajini Sivaram,
> > > > Randall Hauch, Richard, RivenSun, Rob 

[jira] [Created] (KAFKA-13910) Test metadata refresh for Kraft admin client

[dengziming (Jira)]

dengziming created KAFKA-13910:
--

 Summary: Test metadata refresh for Kraft admin client
 Key: KAFKA-13910
 URL: https://issues.apache.org/jira/browse/KAFKA-13910
 Project: Kafka
  Issue Type: Test
Reporter: dengziming


[https://github.com/apache/kafka/pull/12110#discussion_r875418603]

currently we don't get the real controller from MetadtaCache in KRaft mode, we 
should test it in another way



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: [ANNOUNCE] Apache Kafka 3.2.0

[Luke Chen]

Thank you, Bruno!

On Wed, May 18, 2022 at 2:16 AM Guozhang Wang  wrote:

> Congrats to everyone who's contributed to 3.2.0, and special thank you to
> Bruno for running the release!
>
> Guozhang
>
> On Tue, May 17, 2022 at 9:52 AM Bill Bejeck  wrote:
>
> > Thanks for running the release Bruno!
> >
> > On Tue, May 17, 2022 at 12:02 PM Bruno Cadonna 
> wrote:
> >
> > > The Apache Kafka community is pleased to announce the release for
> Apache
> > > Kafka 3.2.0
> > >
> > > * log4j 1.x is replaced with reload4j (KAFKA-9366)
> > > * StandardAuthorizer for KRaft (KIP-801)
> > > * Send a hint to the partition leader to recover the partition
> (KIP-704)
> > > * Top-level error code field in DescribeLogDirsResponse (KIP-784)
> > > * kafka-console-producer writes headers and null values (KIP-798 and
> > > KIP-810)
> > > * JoinGroupRequest and LeaveGroupRequest have a reason attached
> (KIP-800)
> > > * Static membership protocol lets the leader skip assignment (KIP-814)
> > > * Rack-aware standby task assignment in Kafka Streams (KIP-708)
> > > * Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
> > > * Connect APIs list all connector plugins and retrieve their
> > > configuration (KIP-769)
> > > * TimestampConverter SMT supports different unix time precisions
> > (KIP-808)
> > > * Connect source tasks handle producer exceptions (KIP-779)
> > >
> > > All of the changes in this release can be found in the release notes:
> > > https://www.apache.org/dist/kafka/3.2.0/RELEASE_NOTES.html
> > >
> > >
> > > You can download the source and binary release (Scala 2.12 and 2.13)
> > from:
> > > https://kafka.apache.org/downloads#3.2.0
> > >
> > >
> > >
> >
> ---
> > >
> > >
> > > Apache Kafka is a distributed streaming platform with four core APIs:
> > >
> > >
> > > ** The Producer API allows an application to publish a stream of
> records
> > to
> > > one or more Kafka topics.
> > >
> > > ** The Consumer API allows an application to subscribe to one or more
> > > topics and process the stream of records produced to them.
> > >
> > > ** The Streams API allows an application to act as a stream processor,
> > > consuming an input stream from one or more topics and producing an
> > > output stream to one or more output topics, effectively transforming
> the
> > > input streams to output streams.
> > >
> > > ** The Connector API allows building and running reusable producers or
> > > consumers that connect Kafka topics to existing applications or data
> > > systems. For example, a connector to a relational database might
> > > capture every change to a table.
> > >
> > >
> > > With these APIs, Kafka can be used for two broad classes of
> application:
> > >
> > > ** Building real-time streaming data pipelines that reliably get data
> > > between systems or applications.
> > >
> > > ** Building real-time streaming applications that 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 Times, Uber, Yelp, and Zalando, among others.
> > >
> > > A big thank you for the following 113 contributors to this release!
> > >
> > > A. Sophie Blee-Goldman, Adam Kotwasinski, Aleksandr Sorokoumov,
> > > Alexandre Garnier, Alok Nikhil, aSemy, Bounkong Khamphousone, bozhao12,
> > > 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 Wu, Idan Kamara, Ismael Juma,
> > > Jason Gustafson, Jason Koch, Jeff Kim, jiangyuan, Joel Hamill, John
> > > Roesler, Jonathan Albrecht, Jorge Esteban Quilcate Otoya, Josep Prat,
> > > Joseph (Ting-Chou) Lin, José Armando García Sancio, Jules Ivanic,
> Julien
> > > Chanaud, Justin Lee, Justine Olshan, Kamal Chandraprakash, Kate
> Stanley,
> > > keashem, Kirk True, Knowles Atchison, Jr, Konstantine Karantasis,
> > > Kowshik Prakasam, kurtostfeld, Kvicii, Lee Dongjin, Levani Kokhreidze,
> > > lhunyady, Liam Clarke-Hutchinson, liym, loboya~, Lucas Bradstreet,
> > > Ludovic DEHON, Luizfrf3, Luke Chen, Marc Löhe, Matthew Wong, Matthias
> J.
> > > Sax, Michal T, Mickael Maison, Mike Lothian, mkandaswamy, Márton
> > > Sigmond, Nick Telford, Niket, Okada Haruki, Paolo Patierno, Patrick
> > > Stuedi, Philip Nee, Prateek Agarwal, prince-mahajan, Rajini Sivaram,
> > > Randall Hauch, Richard, RivenSun, Rob Leland, Ron Dagostino, Sayantanu
> > > Dey, Stanislav Vodetskyi, sunshujie1990, Tamara Skokova, Tim Patterson,
> > > Tolga H. Dur, Tom Bentley, Tomonari Yamashita, vamossagar12, Vicky
> > > Papavasileiou, Victoria Xia, Vijay Krishna, Vincent Jiang, Walker
> > > Carlson, wangyap, Wenhao Ji, Wenjun Ruan, Xiaobing Fang, 

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

[deng ziming]

Hello Niket,


1. I find the DescribeQuorumResult still contains an 
DescribeQuorumResponseData, which is not allowed as Jose commented, have you 
forgot to change it?

2. You only add an Handle in AdminClient, can you also add an 
`kafka-metadata-quorum.sh` tool to help this?


> On May 17, 2022, at 9:50 AM, Niket Goel  wrote:
> 
> Thanks for the call out David. We will populate these fields for the
> Observers as well. I will clarify this in the KIP.
> 
> On Mon, May 16, 2022 at 1:50 PM David Arthur  wrote:
> 
>> Niket, thanks for the KIP!
>> 
>> Sorry for the late feedback on this, but I just had a quick question. The
>> KIP indicates the two new fields will be set for voters only, however this
>> ReplicaState struct is also used by the Observers in
>> DescribeQuorumResponse. Will we simply fill in -1 for these values, or do
>> we intend to report the last fetch and caught-up time of the observers as
>> well?
>> 
>> Thanks!
>> David
>> 
>> 
>> On Mon, May 16, 2022 at 1:46 PM Niket Goel 
>> wrote:
>> 
>>> Hi all,
>>> 
>>> Thank you for the feedback on this. I have started a voting thread for
>>> this KIP here:
>>> https://lists.apache.org/thread/bkb7gsbxpljh5qh014ztffq7bldjrb2x
>>> 
>>> Thanks
>>> Niket Goel
>>> 
>>> 
>>> From: Niket Goel 
>>> Date: Thursday, May 12, 2022 at 5:25 PM
>>> To: dev@kafka.apache.org 
>>> Subject: Re: [DISCUSS] KIP-836: Addition of Information in
>>> DescribeQuorumResponse about Voter Lag
>>> Appreciate the careful review Jose.!
>>> 
>>> Ack on 1 and 2. Will fix.
>>> 
>>> For number 3 (and I am using [1] as a reference for this discussion), I
>>> think the correct language to use would be:
>>> 
>>> "Whenever a new fetch request
>>> comes in the replica's last caught up time is updated to the time of
>>> this fetch request if it requests an offset greater than or equal to the
>>> leader's
>>> current end offset"
>>> Does that sound right now?
>>> 
>>> Although I think I will go ahead and rewrite the explanation in a way
>> that
>>> is more understandable. Thanks for pointing this out.
>>> 
>>> Thanks
>>> 
>>> [1]
>>> 
>> https://github.com/apache/kafka/blob/fa59be4e770627cd34cef85986b58ad7f606928d/core/src/main/scala/kafka/cluster/Replica.scala#L97
>>> 
>>> 
>>> 
>>> On Thu, May 12, 2022 at 3:20 PM José Armando García Sancio
>>>  wrote:
>>> Thanks for the Kafka improvement Niket.
>>> 
>>> 1. For the fields `LastFetchTime` and `LastCaughtUpTime`, Kafka tends
>>> to use the suffix "Timestamp" when the value is an absolute wall clock
>>> value.
>>> 
>>> 2. The method `result()` for the type `DescribeQuorumResult` returns
>>> the type `DescribeQuorumResponseData`. The types generated from the
>>> RPC JSON schema are internal to Kafka and not exposed to clients. For
>>> the admin client we should use a different type that is explicitly
>>> public. See `org.apache.kafka.client.admin.DescribeTopicsResult` for
>>> an example.
>>> 
>>> 3. The proposed section has his sentence "Whenever a new fetch request
>>> comes in the replica's last caught up time is updated to the time of
>>> the fetch request if it requests an offset greater than the leader's
>>> current end offset." Did you mean "previous fetch time" instead of
>>> "last caught up time"? What do you mean by "requests an offset greater
>>> than the leader's current end offset.?" Excluding diverging logs the
>>> follower fetch offset should never be greater than the leader LEO.
>>> 
>>> Thanks,
>>> -José
>>> 
>>> 
>>> --
>>> - Niket
>>> 
>> 
> 
> 
> -- 
> - Niket

Re: Permission request to contribute

[Luke Chen]

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.
> I'll try again later on.
>
> Thanks for your interest in the Apache Kafka project!
>
> -Bill
>
> On Tue, May 17, 2022 at 5:18 PM Austin Heyne 
> wrote:
>
> > I'd like to request permission to contribute to Kafka
> >
> > Wiki ID: aheyne
> > Jira ID: aheyne
> >
> > Thanks,
> > Austin
> >
> >
> >
>

Jenkins build is back to normal : Kafka » Kafka Branch Builder » trunk #939

[Apache Jenkins Server]

See 

Re: Permission request to contribute

[Bill Bejeck]

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.
I'll try again later on.

Thanks for your interest in the Apache Kafka project!

-Bill

On Tue, May 17, 2022 at 5:18 PM Austin Heyne  wrote:

> I'd like to request permission to contribute to Kafka
>
> Wiki ID: aheyne
> Jira ID: aheyne
>
> Thanks,
> Austin
>
>
>

Permission request to contribute

[Austin Heyne]

I'd like to request permission to contribute to Kafka

Wiki ID: aheyne
Jira ID: aheyne

Thanks,
Austin

Data Engineering Track at ApacheCon (October 3-6, New Orleans) - CFP ends 23/05

[Ismaël Mejía]

Hello,

ApacheCon North America is back in person this year in October.
https://apachecon.com/acna2022/

Together with Jarek Potiuk, we are organizing for the first time a Data
Engineering Track as part of ApacheCon.

You might be wondering why a different track if we already have the Big Data
track. Simple, this new track covers the ‘other’ open-source projects we use to
clean data, orchestrate workloads, do observability, visualization, governance,
data lineage and many other tasks that are part of data engineering and that are
usually not covered by the data processing / database tracks.

If you are curious you can find more details here:
https://s.apache.org/apacheconna-2022-dataeng-track

So why are you getting this message? Well it could be that (1) you are
already a contributor to a project in the data engineering space and you
might be interested in sending your proposal, or (2) you are interested in
integrations of these tools with your existing data tools/projects.

If you are interested you can submit a proposal using the CfP link below.
Don’t forget to choose the Data Engineering Track.
https://apachecon.com/acna2022/cfp.html

The Call for Presentations (CfP) closes in less than one week on May 23th,
2022.

We are looking forward to receiving your submissions and hopefully seeing you in
New Orleans in October.

Thanks,
Ismaël and Jarek

ps. Excuses if you already received this email by a different channel/ML

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

[Jason Gustafson]

+1 Thanks for the KIP!

On Mon, May 16, 2022 at 10:14 AM Niket Goel 
wrote:

> Hi all,
>
> I would like to start a vote for KIP-836:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-836%3A+Addition+of+Information+in+DescribeQuorumResponse+about+Voter+Lag
>
> Thanks
> Niket Goel
>

Re: [ANNOUNCE] Apache Kafka 3.2.0

[Guozhang Wang]

Congrats to everyone who's contributed to 3.2.0, and special thank you to
Bruno for running the release!

Guozhang

On Tue, May 17, 2022 at 9:52 AM Bill Bejeck  wrote:

> Thanks for running the release Bruno!
>
> On Tue, May 17, 2022 at 12:02 PM Bruno Cadonna  wrote:
>
> > The Apache Kafka community is pleased to announce the release for Apache
> > Kafka 3.2.0
> >
> > * log4j 1.x is replaced with reload4j (KAFKA-9366)
> > * StandardAuthorizer for KRaft (KIP-801)
> > * Send a hint to the partition leader to recover the partition (KIP-704)
> > * Top-level error code field in DescribeLogDirsResponse (KIP-784)
> > * kafka-console-producer writes headers and null values (KIP-798 and
> > KIP-810)
> > * JoinGroupRequest and LeaveGroupRequest have a reason attached (KIP-800)
> > * Static membership protocol lets the leader skip assignment (KIP-814)
> > * Rack-aware standby task assignment in Kafka Streams (KIP-708)
> > * Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
> > * Connect APIs list all connector plugins and retrieve their
> > configuration (KIP-769)
> > * TimestampConverter SMT supports different unix time precisions
> (KIP-808)
> > * Connect source tasks handle producer exceptions (KIP-779)
> >
> > All of the changes in this release can be found in the release notes:
> > https://www.apache.org/dist/kafka/3.2.0/RELEASE_NOTES.html
> >
> >
> > You can download the source and binary release (Scala 2.12 and 2.13)
> from:
> > https://kafka.apache.org/downloads#3.2.0
> >
> >
> >
> ---
> >
> >
> > Apache Kafka is a distributed streaming platform with four core APIs:
> >
> >
> > ** The Producer API allows an application to publish a stream of records
> to
> > one or more Kafka topics.
> >
> > ** The Consumer API allows an application to subscribe to one or more
> > topics and process the stream of records produced to them.
> >
> > ** The Streams API allows an application to act as a stream processor,
> > consuming an input stream from one or more topics and producing an
> > output stream to one or more output topics, effectively transforming the
> > input streams to output streams.
> >
> > ** The Connector API allows building and running reusable producers or
> > consumers that connect Kafka topics to existing applications or data
> > systems. For example, a connector to a relational database might
> > capture every change to a table.
> >
> >
> > With these APIs, Kafka can be used for two broad classes of application:
> >
> > ** Building real-time streaming data pipelines that reliably get data
> > between systems or applications.
> >
> > ** Building real-time streaming applications that 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 Times, Uber, Yelp, and Zalando, among others.
> >
> > A big thank you for the following 113 contributors to this release!
> >
> > A. Sophie Blee-Goldman, Adam Kotwasinski, Aleksandr Sorokoumov,
> > Alexandre Garnier, Alok Nikhil, aSemy, Bounkong Khamphousone, bozhao12,
> > 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 Wu, Idan Kamara, Ismael Juma,
> > Jason Gustafson, Jason Koch, Jeff Kim, jiangyuan, Joel Hamill, John
> > Roesler, Jonathan Albrecht, Jorge Esteban Quilcate Otoya, Josep Prat,
> > Joseph (Ting-Chou) Lin, José Armando García Sancio, Jules Ivanic, Julien
> > Chanaud, Justin Lee, Justine Olshan, Kamal Chandraprakash, Kate Stanley,
> > keashem, Kirk True, Knowles Atchison, Jr, Konstantine Karantasis,
> > Kowshik Prakasam, kurtostfeld, Kvicii, Lee Dongjin, Levani Kokhreidze,
> > lhunyady, Liam Clarke-Hutchinson, liym, loboya~, Lucas Bradstreet,
> > Ludovic DEHON, Luizfrf3, Luke Chen, Marc Löhe, Matthew Wong, Matthias J.
> > Sax, Michal T, Mickael Maison, Mike Lothian, mkandaswamy, Márton
> > Sigmond, Nick Telford, Niket, Okada Haruki, Paolo Patierno, Patrick
> > Stuedi, Philip Nee, Prateek Agarwal, prince-mahajan, Rajini Sivaram,
> > Randall Hauch, Richard, RivenSun, Rob Leland, Ron Dagostino, Sayantanu
> > Dey, Stanislav Vodetskyi, sunshujie1990, Tamara Skokova, Tim Patterson,
> > Tolga H. Dur, Tom Bentley, Tomonari Yamashita, vamossagar12, Vicky
> > Papavasileiou, Victoria Xia, Vijay Krishna, Vincent Jiang, Walker
> > Carlson, wangyap, Wenhao Ji, Wenjun Ruan, Xiaobing Fang, Xiaoyue Xue,
> > xuexiaoyue, Yang Yu, yasar03, Yu, Zhang Hongyi, zzccctv, 工业废水, 彭小漪
> >
> > We welcome your help and feedback. For more information on how to
> > report problems, and to get involved, visit the project website at
> > https://kafka.apache.org/
> >
> > Thank you!
> >
> >
> > Regards,
> >
> 

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

[Colin McCabe]

Hi,

I'd like to start the vote on KIP-833: Mark KRaft as Production Ready.
https://cwiki.apache.org/confluence/x/8xKhD

thanks,
Colin

Re: [ANNOUNCE] Apache Kafka 3.2.0

[Bill Bejeck]

Thanks for running the release Bruno!

On Tue, May 17, 2022 at 12:02 PM Bruno Cadonna  wrote:

> The Apache Kafka community is pleased to announce the release for Apache
> Kafka 3.2.0
>
> * log4j 1.x is replaced with reload4j (KAFKA-9366)
> * StandardAuthorizer for KRaft (KIP-801)
> * Send a hint to the partition leader to recover the partition (KIP-704)
> * Top-level error code field in DescribeLogDirsResponse (KIP-784)
> * kafka-console-producer writes headers and null values (KIP-798 and
> KIP-810)
> * JoinGroupRequest and LeaveGroupRequest have a reason attached (KIP-800)
> * Static membership protocol lets the leader skip assignment (KIP-814)
> * Rack-aware standby task assignment in Kafka Streams (KIP-708)
> * Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
> * Connect APIs list all connector plugins and retrieve their
> configuration (KIP-769)
> * TimestampConverter SMT supports different unix time precisions (KIP-808)
> * Connect source tasks handle producer exceptions (KIP-779)
>
> All of the changes in this release can be found in the release notes:
> https://www.apache.org/dist/kafka/3.2.0/RELEASE_NOTES.html
>
>
> You can download the source and binary release (Scala 2.12 and 2.13) from:
> https://kafka.apache.org/downloads#3.2.0
>
>
> ---
>
>
> Apache Kafka is a distributed streaming platform with four core APIs:
>
>
> ** The Producer API allows an application to publish a stream of records to
> one or more Kafka topics.
>
> ** The Consumer API allows an application to subscribe to one or more
> topics and process the stream of records produced to them.
>
> ** The Streams API allows an application to act as a stream processor,
> consuming an input stream from one or more topics and producing an
> output stream to one or more output topics, effectively transforming the
> input streams to output streams.
>
> ** The Connector API allows building and running reusable producers or
> consumers that connect Kafka topics to existing applications or data
> systems. For example, a connector to a relational database might
> capture every change to a table.
>
>
> With these APIs, Kafka can be used for two broad classes of application:
>
> ** Building real-time streaming data pipelines that reliably get data
> between systems or applications.
>
> ** Building real-time streaming applications that 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 Times, Uber, Yelp, and Zalando, among others.
>
> A big thank you for the following 113 contributors to this release!
>
> A. Sophie Blee-Goldman, Adam Kotwasinski, Aleksandr Sorokoumov,
> Alexandre Garnier, Alok Nikhil, aSemy, Bounkong Khamphousone, bozhao12,
> 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 Wu, Idan Kamara, Ismael Juma,
> Jason Gustafson, Jason Koch, Jeff Kim, jiangyuan, Joel Hamill, John
> Roesler, Jonathan Albrecht, Jorge Esteban Quilcate Otoya, Josep Prat,
> Joseph (Ting-Chou) Lin, José Armando García Sancio, Jules Ivanic, Julien
> Chanaud, Justin Lee, Justine Olshan, Kamal Chandraprakash, Kate Stanley,
> keashem, Kirk True, Knowles Atchison, Jr, Konstantine Karantasis,
> Kowshik Prakasam, kurtostfeld, Kvicii, Lee Dongjin, Levani Kokhreidze,
> lhunyady, Liam Clarke-Hutchinson, liym, loboya~, Lucas Bradstreet,
> Ludovic DEHON, Luizfrf3, Luke Chen, Marc Löhe, Matthew Wong, Matthias J.
> Sax, Michal T, Mickael Maison, Mike Lothian, mkandaswamy, Márton
> Sigmond, Nick Telford, Niket, Okada Haruki, Paolo Patierno, Patrick
> Stuedi, Philip Nee, Prateek Agarwal, prince-mahajan, Rajini Sivaram,
> Randall Hauch, Richard, RivenSun, Rob Leland, Ron Dagostino, Sayantanu
> Dey, Stanislav Vodetskyi, sunshujie1990, Tamara Skokova, Tim Patterson,
> Tolga H. Dur, Tom Bentley, Tomonari Yamashita, vamossagar12, Vicky
> Papavasileiou, Victoria Xia, Vijay Krishna, Vincent Jiang, Walker
> Carlson, wangyap, Wenhao Ji, Wenjun Ruan, Xiaobing Fang, Xiaoyue Xue,
> xuexiaoyue, Yang Yu, yasar03, Yu, Zhang Hongyi, zzccctv, 工业废水, 彭小漪
>
> We welcome your help and feedback. For more information on how to
> report problems, and to get involved, visit the project website at
> https://kafka.apache.org/
>
> Thank you!
>
>
> Regards,
>
> Bruno
>

Re: [ANNOUNCE] Apache Kafka 3.2.0

[Mickael Maison]

Thanks Bruno for running this release!


On Tue, May 17, 2022 at 6:02 PM Bruno Cadonna  wrote:
>
> The Apache Kafka community is pleased to announce the release for Apache
> Kafka 3.2.0
>
> * log4j 1.x is replaced with reload4j (KAFKA-9366)
> * StandardAuthorizer for KRaft (KIP-801)
> * Send a hint to the partition leader to recover the partition (KIP-704)
> * Top-level error code field in DescribeLogDirsResponse (KIP-784)
> * kafka-console-producer writes headers and null values (KIP-798 and
> KIP-810)
> * JoinGroupRequest and LeaveGroupRequest have a reason attached (KIP-800)
> * Static membership protocol lets the leader skip assignment (KIP-814)
> * Rack-aware standby task assignment in Kafka Streams (KIP-708)
> * Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
> * Connect APIs list all connector plugins and retrieve their
> configuration (KIP-769)
> * TimestampConverter SMT supports different unix time precisions (KIP-808)
> * Connect source tasks handle producer exceptions (KIP-779)
>
> All of the changes in this release can be found in the release notes:
> https://www.apache.org/dist/kafka/3.2.0/RELEASE_NOTES.html
>
>
> You can download the source and binary release (Scala 2.12 and 2.13) from:
> https://kafka.apache.org/downloads#3.2.0
>
> ---
>
>
> Apache Kafka is a distributed streaming platform with four core APIs:
>
>
> ** The Producer API allows an application to publish a stream of records to
> one or more Kafka topics.
>
> ** The Consumer API allows an application to subscribe to one or more
> topics and process the stream of records produced to them.
>
> ** The Streams API allows an application to act as a stream processor,
> consuming an input stream from one or more topics and producing an
> output stream to one or more output topics, effectively transforming the
> input streams to output streams.
>
> ** The Connector API allows building and running reusable producers or
> consumers that connect Kafka topics to existing applications or data
> systems. For example, a connector to a relational database might
> capture every change to a table.
>
>
> With these APIs, Kafka can be used for two broad classes of application:
>
> ** Building real-time streaming data pipelines that reliably get data
> between systems or applications.
>
> ** Building real-time streaming applications that 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 Times, Uber, Yelp, and Zalando, among others.
>
> A big thank you for the following 113 contributors to this release!
>
> A. Sophie Blee-Goldman, Adam Kotwasinski, Aleksandr Sorokoumov,
> Alexandre Garnier, Alok Nikhil, aSemy, Bounkong Khamphousone, bozhao12,
> 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 Wu, Idan Kamara, Ismael Juma,
> Jason Gustafson, Jason Koch, Jeff Kim, jiangyuan, Joel Hamill, John
> Roesler, Jonathan Albrecht, Jorge Esteban Quilcate Otoya, Josep Prat,
> Joseph (Ting-Chou) Lin, José Armando García Sancio, Jules Ivanic, Julien
> Chanaud, Justin Lee, Justine Olshan, Kamal Chandraprakash, Kate Stanley,
> keashem, Kirk True, Knowles Atchison, Jr, Konstantine Karantasis,
> Kowshik Prakasam, kurtostfeld, Kvicii, Lee Dongjin, Levani Kokhreidze,
> lhunyady, Liam Clarke-Hutchinson, liym, loboya~, Lucas Bradstreet,
> Ludovic DEHON, Luizfrf3, Luke Chen, Marc Löhe, Matthew Wong, Matthias J.
> Sax, Michal T, Mickael Maison, Mike Lothian, mkandaswamy, Márton
> Sigmond, Nick Telford, Niket, Okada Haruki, Paolo Patierno, Patrick
> Stuedi, Philip Nee, Prateek Agarwal, prince-mahajan, Rajini Sivaram,
> Randall Hauch, Richard, RivenSun, Rob Leland, Ron Dagostino, Sayantanu
> Dey, Stanislav Vodetskyi, sunshujie1990, Tamara Skokova, Tim Patterson,
> Tolga H. Dur, Tom Bentley, Tomonari Yamashita, vamossagar12, Vicky
> Papavasileiou, Victoria Xia, Vijay Krishna, Vincent Jiang, Walker
> Carlson, wangyap, Wenhao Ji, Wenjun Ruan, Xiaobing Fang, Xiaoyue Xue,
> xuexiaoyue, Yang Yu, yasar03, Yu, Zhang Hongyi, zzccctv, 工业废水, 彭小漪
>
> We welcome your help and feedback. For more information on how to
> report problems, and to get involved, visit the project website at
> https://kafka.apache.org/
>
> Thank you!
>
>
> Regards,
>
> Bruno

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

[Igor Soarez]

Thanks for this KIP Mickael.

+1 non binding

--
Igor

On Tue, May 17, 2022, at 2:48 PM, Luke Chen wrote:
> 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:
>>
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-827%3A+Expose+logdirs+total+and+usable+space+via+Kafka+API
>>
>> Thanks,
>> Mickael
>>

[ANNOUNCE] Apache Kafka 3.2.0

[Bruno Cadonna]

The Apache Kafka community is pleased to announce the release for Apache 
Kafka 3.2.0


* log4j 1.x is replaced with reload4j (KAFKA-9366)
* StandardAuthorizer for KRaft (KIP-801)
* Send a hint to the partition leader to recover the partition (KIP-704)
* Top-level error code field in DescribeLogDirsResponse (KIP-784)
* kafka-console-producer writes headers and null values (KIP-798 and 
KIP-810)

* JoinGroupRequest and LeaveGroupRequest have a reason attached (KIP-800)
* Static membership protocol lets the leader skip assignment (KIP-814)
* Rack-aware standby task assignment in Kafka Streams (KIP-708)
* Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
* Connect APIs list all connector plugins and retrieve their 
configuration (KIP-769)

* TimestampConverter SMT supports different unix time precisions (KIP-808)
* Connect source tasks handle producer exceptions (KIP-779)

All of the changes in this release can be found in the release notes:
https://www.apache.org/dist/kafka/3.2.0/RELEASE_NOTES.html


You can download the source and binary release (Scala 2.12 and 2.13) from:
https://kafka.apache.org/downloads#3.2.0

---


Apache Kafka is a distributed streaming platform with four core APIs:


** The Producer API allows an application to publish a stream of records to
one or more Kafka topics.

** The Consumer API allows an application to subscribe to one or more
topics and process the stream of records produced to them.

** The Streams API allows an application to act as a stream processor,
consuming an input stream from one or more topics and producing an
output stream to one or more output topics, effectively transforming the
input streams to output streams.

** The Connector API allows building and running reusable producers or
consumers that connect Kafka topics to existing applications or data
systems. For example, a connector to a relational database might
capture every change to a table.


With these APIs, Kafka can be used for two broad classes of application:

** Building real-time streaming data pipelines that reliably get data
between systems or applications.

** Building real-time streaming applications that 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 Times, Uber, Yelp, and Zalando, among others.

A big thank you for the following 113 contributors to this release!

A. Sophie Blee-Goldman, Adam Kotwasinski, Aleksandr Sorokoumov, 
Alexandre Garnier, Alok Nikhil, aSemy, Bounkong Khamphousone, bozhao12, 
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 Wu, Idan Kamara, Ismael Juma, 
Jason Gustafson, Jason Koch, Jeff Kim, jiangyuan, Joel Hamill, John 
Roesler, Jonathan Albrecht, Jorge Esteban Quilcate Otoya, Josep Prat, 
Joseph (Ting-Chou) Lin, José Armando García Sancio, Jules Ivanic, Julien 
Chanaud, Justin Lee, Justine Olshan, Kamal Chandraprakash, Kate Stanley, 
keashem, Kirk True, Knowles Atchison, Jr, Konstantine Karantasis, 
Kowshik Prakasam, kurtostfeld, Kvicii, Lee Dongjin, Levani Kokhreidze, 
lhunyady, Liam Clarke-Hutchinson, liym, loboya~, Lucas Bradstreet, 
Ludovic DEHON, Luizfrf3, Luke Chen, Marc Löhe, Matthew Wong, Matthias J. 
Sax, Michal T, Mickael Maison, Mike Lothian, mkandaswamy, Márton 
Sigmond, Nick Telford, Niket, Okada Haruki, Paolo Patierno, Patrick 
Stuedi, Philip Nee, Prateek Agarwal, prince-mahajan, Rajini Sivaram, 
Randall Hauch, Richard, RivenSun, Rob Leland, Ron Dagostino, Sayantanu 
Dey, Stanislav Vodetskyi, sunshujie1990, Tamara Skokova, Tim Patterson, 
Tolga H. Dur, Tom Bentley, Tomonari Yamashita, vamossagar12, Vicky 
Papavasileiou, Victoria Xia, Vijay Krishna, Vincent Jiang, Walker 
Carlson, wangyap, Wenhao Ji, Wenjun Ruan, Xiaobing Fang, Xiaoyue Xue, 
xuexiaoyue, Yang Yu, yasar03, Yu, Zhang Hongyi, zzccctv, 工业废水, 彭小漪


We welcome your help and feedback. For more information on how to
report problems, and to get involved, visit the project website at
https://kafka.apache.org/

Thank you!


Regards,

Bruno

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

[Ismael Juma]

Hi Mickael,

Thanks for the KIP. Two questions:

1. Is `space` redundant?  is `totalBytes` and `usableBytes` a more concise
description of the same thing?
2. Is usable space a property of the log directory? What if you have
multiple log directories in the same underlying OS partition?

Ismael

On Thu, Apr 7, 2022 at 2:17 AM Mickael Maison 
wrote:

> Hi,
>
> I wrote a small KIP to expose the total and usable space of logdirs
> via the DescribeLogDirs API:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-827%3A+Expose+logdirs+total+and+usable+space+via+Kafka+API
>
> Please take a look and let me know if you have any feedback.
>
> Thanks,
> Mickael
>

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

[Igor Soarez]

I think I have a fix for this in https://github.com/apache/kafka/pull/12174
Please take a look

--
Igor

On Tue, May 17, 2022, at 9:00 AM, Lim Qingwei wrote:
> Thanks for all the tips, I'll look into KAFKA-13907.
>
> On Tue, May 17, 2022 at 3:40 AM deng ziming 
> wrote:
>
>> You can help to solve this bug first if you are free,
>> https://issues.apache.org/jira/browse/KAFKA-13907 <
>> https://issues.apache.org/jira/browse/KAFKA-13907>, since this bug can be
>> reproduced locally, it won't be hard to investigated.
>>
>> > On May 17, 2022, at 12:34 AM, Lim Qingwei  wrote:
>> >
>> > Hi, I am a newbie.
>> >
>> > I noticed Jenkins builds are failing, is this expected?
>> > My PR has some failures, but I don't think they are relevant, how should
>> I
>> > proceed?
>> >
>> > Can I still request for reviews?
>> >
>> > Kind regards
>>
>>

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

[Bruno Cadonna]

Hi Ismael,

Thank you for the clarification!

With "next release" I meant the release after 3.2.0, i.e., 3.3.0 or also 
3.2.1 if we backport the doc change to 3.2.


I admit that this was not entirely clear from my earlier e-mail.

Best,
Bruno


On 17.05.22 16:21, Ismael Juma wrote:

Hi Bruno,

One clarification, the documentation that was updated is not shipped with
the release - it's only on the website. As you said, the website can be
updated at any time.

Ismael

On Mon, May 16, 2022 at 4:16 AM Bruno Cadonna  wrote:


Hi Divij,

The documentation that is shipped with Apache Kafka 3.2.0 cannot be
changed anymore. To change that we would need to create a new release
candidate which would be disproportionate for such a document change.

The PR you linked will be shipped in the docs of the next release. If
someone wants to get this documentation change into the current Apache
Kafka website before the next release, this person could open a PR
against the kafka-site repo.

BTW, the doc line that was changed was not wrong. It was just a bit longer.

Best,
Bruno



On 16.05.22 11:16, Divij Vaidya wrote:

Perhaps, we want to merge in https://github.com/apache/kafka/pull/12164
before this release?

Divij Vaidya



On Mon, May 16, 2022 at 11:30 AM Bruno Cadonna 

wrote:



Mickael,

Thanks a lot!

Totally, missed that!

Best,
Bruno

On 16.05.22 10:13, Mickael Maison wrote:

Hi Bruno,

The blog post looks good.
I just spotted a typo in the description of KIP-769, the endpoint is
"/connector-plugins" instead of "/connect-plugins" (3 times).

Thanks,
Mickael

On Sat, May 14, 2022 at 5:45 PM Federico Valeri 

wrote:


Hi Bruno,

+1 (non binding)

- Checked documentation and blog post
- Ran some client tests using the staged artifacts
- Verified the signing key and sha512 sum
- Built from source
- Ran unit and integration tests

Thanks
Fede

On Thu, May 12, 2022 at 12:03 PM Bruno Cadonna 

wrote:


Hi all,

Please review the blog post for the Apache Kafka 3.2.0 release:





https://blogs.apache.org/preview/kafka/?previewEntry=what-s-new-in-apache8


I will accept comments until Monday, May 16th EOD PT.

Best,
Bruno


On 06.05.22 14:52, 'David Jacot' via kafka-clients wrote:

Thanks for running the release, Bruno.

I performed the following validations:
* Verified all checksums and signatures.
* Built from source and ran unit tests.
* Ran the first quickstart steps for both ZK and KRaft.
* Spotchecked the doc and the Javadocs.

+1 (binding)

Best,
David

On Thu, May 5, 2022 at 10:36 AM Jakub Scholz 

wrote:


+1 (non-binding).

I used the Scala 2.13 binaries and the staged Maven artifacts and

ran

various tests with them. Thanks for doing the release.

Jakub

On Tue, May 3, 2022 at 4:07 PM Bruno Cadonna 

wrote:



Hello Kafka users, developers and client-developers,

This is the second candidate for release of Apache Kafka 3.2.0.

* log4j 1.x is replaced with reload4j (KAFKA-9366)
* StandardAuthorizer for KRaft (KIP-801)
* Send a hint to the partition leader to recover the partition

(KIP-704)

* Top-level error code field in DescribeLogDirsResponse (KIP-784)
* kafka-console-producer writes headers and null values (KIP-798

and

KIP-810)
* JoinGroupRequest and LeaveGroupRequest have a reason attached

(KIP-800)

* Static membership protocol lets the leader skip assignment

(KIP-814)

* Rack-aware standby task assignment in Kafka Streams (KIP-708)
* Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
* Connect APIs list all connector plugins and retrieve their
configuration (KIP-769)
* TimestampConverter SMT supports different unix time precisions

(KIP-808)

* Connect source tasks handle producer exceptions (KIP-779)


Release notes for the 3.2.0 release:


https://home.apache.org/~cadonna/kafka-3.2.0-rc1/RELEASE_NOTES.html


*** Please download, test and vote by Tuesday, May 10th, 9am PDT

Kafka's KEYS file containing PGP keys we use to sign the release:
https://kafka.apache.org/KEYS

* Release artifacts to be voted upon (source and binary):
https://home.apache.org/~cadonna/kafka-3.2.0-rc1/

* Maven artifacts to be voted upon:


https://repository.apache.org/content/groups/staging/org/apache/kafka/


* Javadoc:
https://home.apache.org/~cadonna/kafka-3.2.0-rc1/javadoc/

* Tag to be voted upon (off 3.2 branch) is the 3.2.0 tag:
https://github.com/apache/kafka/releases/tag/3.2.0-rc1

* Documentation:
https://kafka.apache.org/32/documentation.html

* Protocol:
https://kafka.apache.org/32/protocol.html

* Successful Jenkins builds for the 3.2 branch:
Unit/integration tests: I'll share a link once the builds complete
System tests:
https://jenkins.confluent.io/job/system-test-kafka/job/3.2/30/

/**

Thanks,
Bruno

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

[Ismael Juma]

Hi Bruno,

One clarification, the documentation that was updated is not shipped with
the release - it's only on the website. As you said, the website can be
updated at any time.

Ismael

On Mon, May 16, 2022 at 4:16 AM Bruno Cadonna  wrote:

> Hi Divij,
>
> The documentation that is shipped with Apache Kafka 3.2.0 cannot be
> changed anymore. To change that we would need to create a new release
> candidate which would be disproportionate for such a document change.
>
> The PR you linked will be shipped in the docs of the next release. If
> someone wants to get this documentation change into the current Apache
> Kafka website before the next release, this person could open a PR
> against the kafka-site repo.
>
> BTW, the doc line that was changed was not wrong. It was just a bit longer.
>
> Best,
> Bruno
>
>
>
> On 16.05.22 11:16, Divij Vaidya wrote:
> > Perhaps, we want to merge in https://github.com/apache/kafka/pull/12164
> > before this release?
> >
> > Divij Vaidya
> >
> >
> >
> > On Mon, May 16, 2022 at 11:30 AM Bruno Cadonna 
> wrote:
> >
> >> Mickael,
> >>
> >> Thanks a lot!
> >>
> >> Totally, missed that!
> >>
> >> Best,
> >> Bruno
> >>
> >> On 16.05.22 10:13, Mickael Maison wrote:
> >>> Hi Bruno,
> >>>
> >>> The blog post looks good.
> >>> I just spotted a typo in the description of KIP-769, the endpoint is
> >>> "/connector-plugins" instead of "/connect-plugins" (3 times).
> >>>
> >>> Thanks,
> >>> Mickael
> >>>
> >>> On Sat, May 14, 2022 at 5:45 PM Federico Valeri 
> >> wrote:
> 
>  Hi Bruno,
> 
>  +1 (non binding)
> 
>  - Checked documentation and blog post
>  - Ran some client tests using the staged artifacts
>  - Verified the signing key and sha512 sum
>  - Built from source
>  - Ran unit and integration tests
> 
>  Thanks
>  Fede
> 
>  On Thu, May 12, 2022 at 12:03 PM Bruno Cadonna 
> >> wrote:
> >
> > Hi all,
> >
> > Please review the blog post for the Apache Kafka 3.2.0 release:
> >
> >
> >>
> https://blogs.apache.org/preview/kafka/?previewEntry=what-s-new-in-apache8
> >
> > I will accept comments until Monday, May 16th EOD PT.
> >
> > Best,
> > Bruno
> >
> >
> > On 06.05.22 14:52, 'David Jacot' via kafka-clients wrote:
> >> Thanks for running the release, Bruno.
> >>
> >> I performed the following validations:
> >> * Verified all checksums and signatures.
> >> * Built from source and ran unit tests.
> >> * Ran the first quickstart steps for both ZK and KRaft.
> >> * Spotchecked the doc and the Javadocs.
> >>
> >> +1 (binding)
> >>
> >> Best,
> >> David
> >>
> >> On Thu, May 5, 2022 at 10:36 AM Jakub Scholz 
> wrote:
> >>>
> >>> +1 (non-binding).
> >>>
> >>> I used the Scala 2.13 binaries and the staged Maven artifacts and
> ran
> >>> various tests with them. Thanks for doing the release.
> >>>
> >>> Jakub
> >>>
> >>> On Tue, May 3, 2022 at 4:07 PM Bruno Cadonna 
> >> wrote:
> >>>
>  Hello Kafka users, developers and client-developers,
> 
>  This is the second candidate for release of Apache Kafka 3.2.0.
> 
>  * log4j 1.x is replaced with reload4j (KAFKA-9366)
>  * StandardAuthorizer for KRaft (KIP-801)
>  * Send a hint to the partition leader to recover the partition
> >> (KIP-704)
>  * Top-level error code field in DescribeLogDirsResponse (KIP-784)
>  * kafka-console-producer writes headers and null values (KIP-798
> and
>  KIP-810)
>  * JoinGroupRequest and LeaveGroupRequest have a reason attached
> >> (KIP-800)
>  * Static membership protocol lets the leader skip assignment
> >> (KIP-814)
>  * Rack-aware standby task assignment in Kafka Streams (KIP-708)
>  * Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
>  * Connect APIs list all connector plugins and retrieve their
>  configuration (KIP-769)
>  * TimestampConverter SMT supports different unix time precisions
> >> (KIP-808)
>  * Connect source tasks handle producer exceptions (KIP-779)
> 
> 
>  Release notes for the 3.2.0 release:
> 
> https://home.apache.org/~cadonna/kafka-3.2.0-rc1/RELEASE_NOTES.html
> 
>  *** Please download, test and vote by Tuesday, May 10th, 9am PDT
> 
>  Kafka's KEYS file containing PGP keys we use to sign the release:
>  https://kafka.apache.org/KEYS
> 
>  * Release artifacts to be voted upon (source and binary):
>  https://home.apache.org/~cadonna/kafka-3.2.0-rc1/
> 
>  * Maven artifacts to be voted upon:
> 
> >> https://repository.apache.org/content/groups/staging/org/apache/kafka/
> 
>  * Javadoc:
>  https://home.apache.org/~cadonna/kafka-3.2.0-rc1/javadoc/
> 
>  * Tag to be voted upon (off 

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

[Federico Valeri]

+1 (non binding)

Thanks.

On Tue, May 17, 2022 at 3:47 PM Mickael Maison  wrote:
>
> Hi,
>
> I'd like to start a vote on KIP-830 which proposes a method for a
> method for disabling JMXReporter and making JMXReporter behave like
> other reporters in the next major release when it will need to be
> explicitly listed in metric.reporters to be enabled.
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-830%3A+Allow+disabling+JMX+Reporter
>
> Let me know if you have feedback,
>
> Thanks,
> Mickael

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

[Ismael Juma]

Thanks Mickael. Quick question:

"When set to true, a warning will be printed to indicate this setting is
deprecated and recommend using metric.reporters instead."

The config defaults to true, so I think we should be a bit clearer when the
warning is printed. I was thinking we would print the warning if either:

* The config is set to true explicitly (there isn't a reason to do this on
its own since it's the default)

OR

* The config is true due to the default and metrics.reporters is configured
without the jmx reporter (this particular scenario would have different
behavior in AK 4.0)

Does this make sense?

Ismael

On Tue, May 17, 2022 at 6:47 AM Mickael Maison 
wrote:

> Hi,
>
> I'd like to start a vote on KIP-830 which proposes a method for a
> method for disabling JMXReporter and making JMXReporter behave like
> other reporters in the next major release when it will need to be
> explicitly listed in metric.reporters to be enabled.
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-830%3A+Allow+disabling+JMX+Reporter
>
> Let me know if you have feedback,
>
> Thanks,
> Mickael
>

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

[Luke Chen]

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:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-827%3A+Expose+logdirs+total+and+usable+space+via+Kafka+API
>
> Thanks,
> Mickael
>

[VOTE] KIP-830: Allow disabling JMX Reporter

[Mickael Maison]

Hi,

I'd like to start a vote on KIP-830 which proposes a method for a
method for disabling JMXReporter and making JMXReporter behave like
other reporters in the next major release when it will need to be
explicitly listed in metric.reporters to be enabled.

https://cwiki.apache.org/confluence/display/KAFKA/KIP-830%3A+Allow+disabling+JMX+Reporter

Let me know if you have feedback,

Thanks,
Mickael

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

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 627271 lines...]
[2022-05-17T13:25:52.058Z] > Task :streams:javadoc
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:890:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:919:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:939:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:854:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:890:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:919:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:939:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/Produced.java:84:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/Produced.java:136:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/Produced.java:147:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/Repartitioned.java:101:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/kstream/Repartitioned.java:167:
 warning - Tag @link: reference not found: DefaultPartitioner
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/StreamsConfig.java:443:
 warning - @statestore.cache.max.bytes is an unknown tag.
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/StreamsConfig.java:443:
 warning - @statestore.cache.max.bytes is an unknown tag.
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/StreamsConfig.java:443:
 warning - @statestore.cache.max.bytes is an unknown tag.
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/TopologyConfig.java:61:
 warning - Tag @link: missing '#': "org.apache.kafka.streams.StreamsBuilder()"
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/TopologyConfig.java:61:
 warning - Tag @link: can't find org.apache.kafka.streams.StreamsBuilder() in 
org.apache.kafka.streams.TopologyConfig
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/query/Position.java:44:
 warning - Tag @link: can't find query(Query,
[2022-05-17T13:25:52.058Z]  PositionBound, boolean) in 
org.apache.kafka.streams.processor.StateStore
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:44:
 warning - Tag @link: can't find query(Query, PositionBound, boolean) in 
org.apache.kafka.streams.processor.StateStore
[2022-05-17T13:25:52.058Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/query/QueryResult.java:36:
 warning - Tag @link: can't find query(Query, PositionBound, boolean) in 
org.apache.kafka.streams.processor.StateStore
[2022-05-17T13:25:52.058Z] 

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

[Mickael Maison]

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:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-827%3A+Expose+logdirs+total+and+usable+space+via+Kafka+API

Thanks,
Mickael

Re: [VOTE] KIP-714: Client Metrics and Observability

[Magnus Edenhill]

Hey all,

It's that time of year again where we re-restart this vote thread after
some additional
discussions on the disco thread and minor adjustments to the
KIP.

We're currently at +5 (non-binding) and -1 (non-binding) votes.

Please cast your votes, people.


Thanks,
Magnus


Den tors 3 mars 2022 kl 15:39 skrev Julien Chanaud :

> +1
> As a member of a team which operates several Kafka clusters, I am
> unequipped when it comes to troubleshooting issues with project teams
> that did not understand the importance of configuring client-side
> monitoring.
> Kafka represents a fraction of their work and they don't have enough
> experience, time or interest in trying to understand the meaning behind
> every metric.
>
> I stand 100% behind what Colin stated back in June in the Discuss thread :
>
> > Magnus and I explained a few times the reasons why it does matter. Within
> > most organizations, there are usually several teams using clients, which
> > are separate from the team which maintains the Kafka cluster. The Kafka
> > team has the Kafka experts, which makes it the best place to centralize
> > collecting and analyzing Kafka metrics.
>
>
> Thanks for this KIP.
>
> Le mer. 26 janv. 2022 à 16:01, rifer...@riferrei.com <
> rifer...@riferrei.com>
> a écrit :
>
> > +1
> >
> > I think this KIP solves a problem that has been around for some time with
> > Kafka deployments, which is the ability to assess the current state of a
> > Kafka architecture but looking at the whole picture. I also share other
> > folks' concerns regarding adding runtime dependencies to the clients;
> this
> > may be problematic for large deployments. Still, I think it is worth
> > refactoring.
> >
> > IMHO, it is a fair trade-off.
> >
> > — Ricardo
> >
> > > On Jan 26, 2022, at 9:34 AM, Magnus Edenhill 
> wrote:
> > >
> > > Hi all,
> > >
> > > it's been a while and there's been some more discussions of the KIP
> which
> > > have been
> > > addressed on the KIP page.
> > >
> > > I think it's a good time to revive this vote thread and get things
> > moving.
> > >
> > > We're currently at +3 (non-binding) and -1 (non-binding) votes.
> > >
> > > Regards,
> > > Magnus
> > >
> > >
> > > Den mån 1 nov. 2021 kl 21:19 skrev J Rivers :
> > >
> > >> +1
> > >>
> > >> Thank you for the KIP!
> > >>
> > >> Our organization runs kafka at large scale in a multi-tenant
> > configuration.
> > >> We actually have many other enterprises connecting up to our system to
> > >> retrieve stream data. These feeds vary greatly in volume and velocity.
> > The
> > >> peak rates are a multiplicative factor of the nominal.  There is
> extreme
> > >> skew in our datasets in a number of ways.
> > >>
> > >> We don't have time to work with every new internal/external client to
> > tune
> > >> their feeds. They need to be able to take one of the many kafka
> clients
> > and
> > >> go off to the races.
> > >>
> > >> Being able to retrieve client metrics would be invaluable here as it's
> > hard
> > >> and time consuming to communicate out of the enterprise walls.
> > >>
> > >> This KIP is important to us to expand the use of our datasets
> internally
> > >> and outside the borders of the enterprise. Our clients like the
> > performance
> > >> and data safeties related to the kafka connection. The observability
> has
> > >> been a problem...
> > >>
> > >> Jonathan Rivers
> > >> jrivers...@gmail.com
> > >>
> > >>
> > >>
> > >>
> > >> On Mon, Oct 18, 2021 at 11:56 PM Ryanne Dolan 
> > >> wrote:
> > >>
> > >>> -1
> > >>>
> > >>> Ryanne
> > >>>
> > >>> On Mon, Oct 18, 2021, 4:30 AM Magnus Edenhill 
> > >> wrote:
> > >>>
> >  Hi all,
> > 
> >  I'd like to start a vote on KIP-714.
> >  https://cwiki.apache.org/confluence/x/2xRRCg
> > 
> >  Discussion thread:
> >  https://www.mail-archive.com/dev@kafka.apache.org/msg119000.html
> > 
> >  Thanks,
> >  Magnus
> > 
> > >>>
> > >>
> >
> >
>

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #937

[Apache Jenkins Server]

See 

[GitHub] [kafka-site] milindmantri opened a new pull request, #412: MINOR: Fix DSL typo in streams docs

[GitBox]

milindmantri opened a new pull request, #412:
URL: https://github.com/apache/kafka-site/pull/412

   Reference: apache/kafka#12152
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

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

[Florian Blumenstein (Jira)]

Florian Blumenstein created KAFKA-13909:
---

 Summary: Restart Kafka in KRaft mode with ACLs ends in a 
RuntimeException
 Key: KAFKA-13909
 URL: https://issues.apache.org/jira/browse/KAFKA-13909
 Project: Kafka
  Issue Type: Bug
  Components: kraft
Affects Versions: 3.2.0
 Environment: Running Kafka in a Docker container
Reporter: Florian Blumenstein
 Attachments: kafka.log, server.properties

Running Kafka in KRaft mode works for the initial startup. When restarting 
Kafka it ends in a RuntimeException:
[2022-05-17 08:26:40,959] ERROR [BrokerServer id=1] Fatal error during broker 
startup. Prepare to shutdown (kafka.server.BrokerServer)
java.util.concurrent.ExecutionException: java.lang.RuntimeException: An ACL 
with ID toAvM0TbTfWRmS1kjknRaA already exists.
        at java.base/java.util.concurrent.CompletableFuture.reportGet(Unknown 
Source)
        at java.base/java.util.concurrent.CompletableFuture.get(Unknown Source)
        at kafka.server.BrokerServer.startup(BrokerServer.scala:426)
        at 
kafka.server.KafkaRaftServer.$anonfun$startup$2(KafkaRaftServer.scala:114)
        at 
kafka.server.KafkaRaftServer.$anonfun$startup$2$adapted(KafkaRaftServer.scala:114)
        at scala.Option.foreach(Option.scala:437)
        at kafka.server.KafkaRaftServer.startup(KafkaRaftServer.scala:114)
        at kafka.Kafka$.main(Kafka.scala:109)
        at kafka.Kafka.main(Kafka.scala)
Caused by: java.lang.RuntimeException: An ACL with ID toAvM0TbTfWRmS1kjknRaA 
already exists.
        at 
org.apache.kafka.metadata.authorizer.StandardAuthorizerData.addAcl(StandardAuthorizerData.java:169)
        at 
org.apache.kafka.metadata.authorizer.StandardAuthorizer.addAcl(StandardAuthorizer.java:83)
        at 
kafka.server.metadata.BrokerMetadataPublisher.$anonfun$publish$19(BrokerMetadataPublisher.scala:234)
        at java.base/java.util.LinkedHashMap$LinkedEntrySet.forEach(Unknown 
Source)
        at 
kafka.server.metadata.BrokerMetadataPublisher.$anonfun$publish$18(BrokerMetadataPublisher.scala:232)
        at 
kafka.server.metadata.BrokerMetadataPublisher.$anonfun$publish$18$adapted(BrokerMetadataPublisher.scala:221)
        at scala.Option.foreach(Option.scala:437)
        at 
kafka.server.metadata.BrokerMetadataPublisher.publish(BrokerMetadataPublisher.scala:221)
        at 
kafka.server.metadata.BrokerMetadataListener.kafka$server$metadata$BrokerMetadataListener$$publish(BrokerMetadataListener.scala:258)
        at 
kafka.server.metadata.BrokerMetadataListener$StartPublishingEvent.run(BrokerMetadataListener.scala:241)
        at 
org.apache.kafka.queue.KafkaEventQueue$EventContext.run(KafkaEventQueue.java:121)
        at 
org.apache.kafka.queue.KafkaEventQueue$EventHandler.handleEvents(KafkaEventQueue.java:200)
        at 
org.apache.kafka.queue.KafkaEventQueue$EventHandler.run(KafkaEventQueue.java:173)
        at java.base/java.lang.Thread.run(Unknown Source)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[Luke Chen (Jira)]

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
 Project: Kafka
  Issue Type: Improvement
Reporter: Luke Chen


Before [#11969|https://github.com/apache/kafka/pull/11969], We will throw an 
{{ExecutionException(KafkaStorageException)}} in {{{}BrokerServer.startup{}}}, 
and we'll catch the exception and rethrow the cause by:
{code:java}
throw if (e.isInstanceOf[ExecutionException]) e.getCause else e{code}
 

After [#11969|https://github.com/apache/kafka/pull/11969], We will throw a 
{{RuntimeException(ExecutionException(KafkaStorageException)). But the catch 
logic didn't change. That means, if the exception is RuntimeException, we won't 
throw only the cause, but all the exception chains. }}

 

We should update it and add tests for it.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[Luke Chen (Jira)]

 [ 
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 failing 
> ServerShutdownTest.testCleanShutdownAfterFailedStartupDueToCorruptLogs
> --
>
> Key: KAFKA-13905
> URL: https://issues.apache.org/jira/browse/KAFKA-13905
> Project: Kafka
>  Issue Type: Test
>Reporter: Luke Chen
>Assignee: dengziming
>Priority: Major
> Fix For: 3.3.0
>
>
> h3. Error Message
> org.opentest4j.AssertionFailedError: Unexpected exception 
> java.lang.RuntimeException: Received a fatal error while waiting for the 
> broker to catch up with the current cluster metadata. ==> expected:  
> but was: 
> h3. Stacktrace
> org.opentest4j.AssertionFailedError: Unexpected exception 
> java.lang.RuntimeException: Received a fatal error while waiting for the 
> broker to catch up with the current cluster metadata. ==> expected:  
> but was:  at 
> org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55) at 
> org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:40) at 
> org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:210) at 
> kafka.server.ServerShutdownTest.verifyCleanShutdownAfterFailedStartup(ServerShutdownTest.scala:198)
>  at 
> kafka.server.ServerShutdownTest.testCleanShutdownAfterFailedStartupDueToCorruptLogs(ServerShutdownTest.scala:168)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[Lim Qingwei]

Thanks for all the tips, I'll look into KAFKA-13907.

On Tue, May 17, 2022 at 3:40 AM deng ziming 
wrote:

> You can help to solve this bug first if you are free,
> https://issues.apache.org/jira/browse/KAFKA-13907 <
> https://issues.apache.org/jira/browse/KAFKA-13907>, since this bug can be
> reproduced locally, it won't be hard to investigated.
>
> > On May 17, 2022, at 12:34 AM, Lim Qingwei  wrote:
> >
> > Hi, I am a newbie.
> >
> > I noticed Jenkins builds are failing, is this expected?
> > My PR has some failures, but I don't think they are relevant, how should
> I
> > proceed?
> >
> > Can I still request for reviews?
> >
> > Kind regards
>
>

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

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 547120 lines...]
[2022-05-17T02:22:57.968Z] [INFO] --- maven-gpg-plugin:1.6:sign 
(sign-artifacts) @ streams-quickstart ---
[2022-05-17T02:22:57.968Z] [INFO] 
[2022-05-17T02:22:57.968Z] [INFO] --- maven-install-plugin:2.5.2:install 
(default-install) @ streams-quickstart ---
[2022-05-17T02:22:57.968Z] [INFO] Installing 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/quickstart/pom.xml
 to 
/home/jenkins/.m2/repository/org/apache/kafka/streams-quickstart/3.3.0-SNAPSHOT/streams-quickstart-3.3.0-SNAPSHOT.pom
[2022-05-17T02:22:57.968Z] [INFO] 
[2022-05-17T02:22:57.968Z] [INFO] --< 
org.apache.kafka:streams-quickstart-java >--
[2022-05-17T02:22:57.968Z] [INFO] Building streams-quickstart-java 
3.3.0-SNAPSHOT[2/2]
[2022-05-17T02:22:57.968Z] [INFO] --[ maven-archetype 
]---
[2022-05-17T02:22:57.968Z] [INFO] 
[2022-05-17T02:22:57.968Z] [INFO] --- maven-clean-plugin:3.0.0:clean 
(default-clean) @ streams-quickstart-java ---
[2022-05-17T02:22:57.968Z] [INFO] 
[2022-05-17T02:22:57.968Z] [INFO] --- maven-remote-resources-plugin:1.5:process 
(process-resource-bundles) @ streams-quickstart-java ---
[2022-05-17T02:22:57.968Z] [INFO] 
[2022-05-17T02:22:57.968Z] [INFO] --- maven-resources-plugin:2.7:resources 
(default-resources) @ streams-quickstart-java ---
[2022-05-17T02:22:57.968Z] [INFO] Using 'UTF-8' encoding to copy filtered 
resources.
[2022-05-17T02:22:57.968Z] [INFO] Copying 6 resources
[2022-05-17T02:22:57.968Z] [INFO] Copying 3 resources
[2022-05-17T02:22:57.968Z] [INFO] 
[2022-05-17T02:22:57.968Z] [INFO] --- maven-resources-plugin:2.7:testResources 
(default-testResources) @ streams-quickstart-java ---
[2022-05-17T02:22:57.968Z] [INFO] Using 'UTF-8' encoding to copy filtered 
resources.
[2022-05-17T02:22:58.906Z] [INFO] Copying 2 resources
[2022-05-17T02:22:58.906Z] [INFO] Copying 3 resources
[2022-05-17T02:22:58.906Z] [INFO] 
[2022-05-17T02:22:58.906Z] [INFO] --- maven-archetype-plugin:2.2:jar 
(default-jar) @ streams-quickstart-java ---
[2022-05-17T02:22:58.906Z] [INFO] Building archetype jar: 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/quickstart/java/target/streams-quickstart-java-3.3.0-SNAPSHOT
[2022-05-17T02:22:58.906Z] [INFO] 
[2022-05-17T02:22:58.906Z] [INFO] --- maven-site-plugin:3.5.1:attach-descriptor 
(attach-descriptor) @ streams-quickstart-java ---
[2022-05-17T02:22:58.906Z] [INFO] 
[2022-05-17T02:22:58.906Z] [INFO] --- 
maven-archetype-plugin:2.2:integration-test (default-integration-test) @ 
streams-quickstart-java ---
[2022-05-17T02:22:58.906Z] [INFO] 
[2022-05-17T02:22:58.906Z] [INFO] --- maven-gpg-plugin:1.6:sign 
(sign-artifacts) @ streams-quickstart-java ---
[2022-05-17T02:22:58.906Z] [INFO] 
[2022-05-17T02:22:58.906Z] [INFO] --- maven-install-plugin:2.5.2:install 
(default-install) @ streams-quickstart-java ---
[2022-05-17T02:22:58.906Z] [INFO] Installing 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/quickstart/java/target/streams-quickstart-java-3.3.0-SNAPSHOT.jar
 to 
/home/jenkins/.m2/repository/org/apache/kafka/streams-quickstart-java/3.3.0-SNAPSHOT/streams-quickstart-java-3.3.0-SNAPSHOT.jar
[2022-05-17T02:22:58.906Z] [INFO] Installing 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/quickstart/java/pom.xml
 to 
/home/jenkins/.m2/repository/org/apache/kafka/streams-quickstart-java/3.3.0-SNAPSHOT/streams-quickstart-java-3.3.0-SNAPSHOT.pom
[2022-05-17T02:22:58.906Z] [INFO] 
[2022-05-17T02:22:58.906Z] [INFO] --- 
maven-archetype-plugin:2.2:update-local-catalog (default-update-local-catalog) 
@ streams-quickstart-java ---
[2022-05-17T02:22:58.906Z] [INFO] 

[2022-05-17T02:22:58.906Z] [INFO] Reactor Summary for Kafka Streams :: 
Quickstart 3.3.0-SNAPSHOT:
[2022-05-17T02:22:58.906Z] [INFO] 
[2022-05-17T02:22:58.906Z] [INFO] Kafka Streams :: Quickstart 
 SUCCESS [  2.651 s]
[2022-05-17T02:22:58.906Z] [INFO] streams-quickstart-java 
 SUCCESS [  0.857 s]
[2022-05-17T02:22:58.906Z] [INFO] 

[2022-05-17T02:22:58.906Z] [INFO] BUILD SUCCESS
[2022-05-17T02:22:58.906Z] [INFO] 

[2022-05-17T02:22:58.906Z] [INFO] Total time:  3.859 s
[2022-05-17T02:22:58.906Z] [INFO] Finished at: 2022-05-17T02:22:58Z
[2022-05-17T02:22:58.906Z] [INFO] 

[Pipeline] dir
[2022-05-17T02:22:59.422Z] Running in 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/quickstart/test-streams-archetype
[Pipeline] {
[Pipeline] sh
[2022-05-17T02:23:02.167Z] + echo Y