subject:"Re\: \[VOTE\] 3.7.0 RC4"

Re: [VOTE] 3.7.0 RC4

2024-03-01 Thread Stanislav Kozlovski

Makes sense, thanks Ismael. I've updated it.

We are released now! Thank you to all who contributed!

There are two final things to do with relation to the release as per the
wiki - and that is introduce 3.7 to the respective compatibility system
tests for Core, Clients and Streams.

Here are the PRs for that:
- https://github.com/apache/kafka/pull/15452
- https://github.com/apache/kafka/pull/15453

On Wed, Feb 28, 2024 at 4:17 PM Ismael Juma  wrote:

> Hi,
>
> mvnrepository doesn't matter, we should update the guidelines to remove it.
> All that matters is that it has reached the maven central repository.
>
> Ismael
>
> On Tue, Feb 27, 2024 at 9:49 AM Stanislav Kozlovski
>  wrote:
>
> > The thinking is that it is available for use - and it is in maven
> central -
> > https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13 - but
> > the
> > mvnrepository seems to be an unofficial website that offers a nice UI for
> > accessing maven central. The release is in the latter -
> > https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13
> >
> > On Tue, Feb 27, 2024 at 6:35 PM Divij Vaidya 
> > wrote:
> >
> > > We wait before making the announcement. The rationale is that there is
> > not
> > > much point announcing a release if folks cannot start using that
> version
> > > artifacts immediately.
> > >
> > > See "Wait for about a day for the artifacts to show up in apache mirror
> > > (releases, public group) and maven central (mvnrepository.com or
> > maven.org
> > > )."
> > > in the release process wiki.
> > >
> > > --
> > > Divij Vaidya
> > >
> > >
> > >
> > > On Tue, Feb 27, 2024 at 4:43 PM Stanislav Kozlovski
> > >  wrote:
> > >
> > > > Hey all,
> > > >
> > > > Everything site-related is merged.
> > > >
> > > > I have been following the final steps of the release process.
> > > > - Docker contains the release -
> > > https://hub.docker.com/r/apache/kafka/tags
> > > > - Maven central contains the release -
> > > >
> > > >
> > >
> >
> https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13/3.7.0/versions
> > > > .
> > > > Note it says Feb 9 publish date, but it was just published. The RC4
> > files
> > > > were created on Feb 9 though, so I assume that's why it says that
> > > > - mvnrepository is NOT yet up to date -
> > > > https://mvnrepository.com/artifact/org.apache.kafka/kafka-clients
> and
> > > > https://mvnrepository.com/artifact/org.apache.kafka/kafka
> > > >
> > > > Am I free to announce the release, or should I wait more for
> > > MVNRepository
> > > > to get up to date? For what it's worth, I "Released" the files 24
> hours
> > > ago
> > > >
> > > > On Mon, Feb 26, 2024 at 10:42 AM Stanislav Kozlovski <
> > > > stanis...@confluent.io>
> > > > wrote:
> > > >
> > > > >
> > > > > This vote passes with *10 +1 votes* (3 bindings) and no 0 or -1
> > votes.
> > > > >
> > > > > +1 votes
> > > > >
> > > > > PMC Members (binding):
> > > > > * Mickael Maison
> > > > > * Justine Olshan
> > > > > * Divij Vaidya
> > > > >
> > > > > Community (non-binding):
> > > > > * Proven Provenzano
> > > > > * Federico Valeri
> > > > > * Vedarth Sharma
> > > > > * Andrew Schofield
> > > > > * Paolo Patierno
> > > > > * Jakub Scholz
> > > > > * Josep Prat
> > > > >
> > > > > 
> > > > >
> > > > > 0 votes
> > > > >
> > > > > * No votes
> > > > >
> > > > > 
> > > > >
> > > > > -1 votes
> > > > >
> > > > > * No votes
> > > > >
> > > > > 
> > > > >
> > > > > Vote thread:
> > > > > https://lists.apache.org/thread/71djwz292y2lzgwzm7n6n8o7x56zbgh9
> > > > >
> > > > > I'll continue with the release process and the release announcement
> > > will
> > > > > follow ASAP.
> > > > >
> > > > > Best,
> > > > > Stanislav
> > > > >
> > > > > On Sun, Feb 25, 2024 at 7:08 PM Mickael Maison <
> > > mickael.mai...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >> Thanks for sorting out the docs issues.
> > > > >> +1 (binding)
> > > > >>
> > > > >> Mickael
> > > > >>
> > > > >> On Fri, Feb 23, 2024 at 11:50 AM Stanislav Kozlovski
> > > > >>  wrote:
> > > > >> >
> > > > >> > Some quick updates:
> > > > >> >
> > > > >> > There were some inconsistencies between the documentation in the
> > > > >> > apache/kafka repo and the one in kafka-site. The process is such
> > > that
> > > > >> the
> > > > >> > apache/kafka docs are the source of truth, but we had a few
> > > > divergences
> > > > >> in
> > > > >> > the other repo. I have worked on correcting those with:
> > > > >> > - MINOR: Reconcile upgrade.html with kafka-site/36's version
> > > > >> >  and cherry-picked
> it
> > > > into
> > > > >> the
> > > > >> > 3.6 and 3.7 branches too
> > > > >> >
> > > > >> > Additionally, the 3.7 upgrade notes have been merged in
> > > apache/kafka -
> > > > >> MINOR:
> > > > >> > Add 3.7 upgrade notes <
> > > > https://github.com/apache/kafka/pull/15407/files
> > > > >> >.
> > > > >> >
> > > > >> > With that, I have opened a PR to move them to

Re: [VOTE] 3.7.0 RC4

2024-02-28 Thread Ismael Juma

Hi,

mvnrepository doesn't matter, we should update the guidelines to remove it.
All that matters is that it has reached the maven central repository.

Ismael

On Tue, Feb 27, 2024 at 9:49 AM Stanislav Kozlovski
 wrote:

> The thinking is that it is available for use - and it is in maven central -
> https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13 - but
> the
> mvnrepository seems to be an unofficial website that offers a nice UI for
> accessing maven central. The release is in the latter -
> https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13
>
> On Tue, Feb 27, 2024 at 6:35 PM Divij Vaidya 
> wrote:
>
> > We wait before making the announcement. The rationale is that there is
> not
> > much point announcing a release if folks cannot start using that version
> > artifacts immediately.
> >
> > See "Wait for about a day for the artifacts to show up in apache mirror
> > (releases, public group) and maven central (mvnrepository.com or
> maven.org
> > )."
> > in the release process wiki.
> >
> > --
> > Divij Vaidya
> >
> >
> >
> > On Tue, Feb 27, 2024 at 4:43 PM Stanislav Kozlovski
> >  wrote:
> >
> > > Hey all,
> > >
> > > Everything site-related is merged.
> > >
> > > I have been following the final steps of the release process.
> > > - Docker contains the release -
> > https://hub.docker.com/r/apache/kafka/tags
> > > - Maven central contains the release -
> > >
> > >
> >
> https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13/3.7.0/versions
> > > .
> > > Note it says Feb 9 publish date, but it was just published. The RC4
> files
> > > were created on Feb 9 though, so I assume that's why it says that
> > > - mvnrepository is NOT yet up to date -
> > > https://mvnrepository.com/artifact/org.apache.kafka/kafka-clients and
> > > https://mvnrepository.com/artifact/org.apache.kafka/kafka
> > >
> > > Am I free to announce the release, or should I wait more for
> > MVNRepository
> > > to get up to date? For what it's worth, I "Released" the files 24 hours
> > ago
> > >
> > > On Mon, Feb 26, 2024 at 10:42 AM Stanislav Kozlovski <
> > > stanis...@confluent.io>
> > > wrote:
> > >
> > > >
> > > > This vote passes with *10 +1 votes* (3 bindings) and no 0 or -1
> votes.
> > > >
> > > > +1 votes
> > > >
> > > > PMC Members (binding):
> > > > * Mickael Maison
> > > > * Justine Olshan
> > > > * Divij Vaidya
> > > >
> > > > Community (non-binding):
> > > > * Proven Provenzano
> > > > * Federico Valeri
> > > > * Vedarth Sharma
> > > > * Andrew Schofield
> > > > * Paolo Patierno
> > > > * Jakub Scholz
> > > > * Josep Prat
> > > >
> > > > 
> > > >
> > > > 0 votes
> > > >
> > > > * No votes
> > > >
> > > > 
> > > >
> > > > -1 votes
> > > >
> > > > * No votes
> > > >
> > > > 
> > > >
> > > > Vote thread:
> > > > https://lists.apache.org/thread/71djwz292y2lzgwzm7n6n8o7x56zbgh9
> > > >
> > > > I'll continue with the release process and the release announcement
> > will
> > > > follow ASAP.
> > > >
> > > > Best,
> > > > Stanislav
> > > >
> > > > On Sun, Feb 25, 2024 at 7:08 PM Mickael Maison <
> > mickael.mai...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> Thanks for sorting out the docs issues.
> > > >> +1 (binding)
> > > >>
> > > >> Mickael
> > > >>
> > > >> On Fri, Feb 23, 2024 at 11:50 AM Stanislav Kozlovski
> > > >>  wrote:
> > > >> >
> > > >> > Some quick updates:
> > > >> >
> > > >> > There were some inconsistencies between the documentation in the
> > > >> > apache/kafka repo and the one in kafka-site. The process is such
> > that
> > > >> the
> > > >> > apache/kafka docs are the source of truth, but we had a few
> > > divergences
> > > >> in
> > > >> > the other repo. I have worked on correcting those with:
> > > >> > - MINOR: Reconcile upgrade.html with kafka-site/36's version
> > > >> >  and cherry-picked it
> > > into
> > > >> the
> > > >> > 3.6 and 3.7 branches too
> > > >> >
> > > >> > Additionally, the 3.7 upgrade notes have been merged in
> > apache/kafka -
> > > >> MINOR:
> > > >> > Add 3.7 upgrade notes <
> > > https://github.com/apache/kafka/pull/15407/files
> > > >> >.
> > > >> >
> > > >> > With that, I have opened a PR to move them to the kafka-site
> > > repository
> > > >> -
> > > >> > https://github.com/apache/kafka-site/pull/587. That is awaiting
> > > review.
> > > >> >
> > > >> > Similarly, the 3.7 blog post is ready for review again
> > > >> >  and awaiting a
> > review
> > > >> on 37:
> > > >> > Update default docs to point to the 3.7.0 release docs
> > > >> > 
> > > >> >
> > > >> > I also have a WIP for fixing the 3.6 docs in the kafka-site repo
> > > >> > . This isn't
> really
> > > >> related
> > > >> > to the release, but it's good to do.
> > > >> >
> > > >> > On Wed, Feb 21, 2024 at 4:55 AM Luke Chen 
> > wrote:
> > > >> >
> > > >> > >

Re: [VOTE] 3.7.0 RC4

2024-02-27 Thread Stanislav Kozlovski

The thinking is that it is available for use - and it is in maven central -
https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13 - but the
mvnrepository seems to be an unofficial website that offers a nice UI for
accessing maven central. The release is in the latter -
https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13

On Tue, Feb 27, 2024 at 6:35 PM Divij Vaidya 
wrote:

> We wait before making the announcement. The rationale is that there is not
> much point announcing a release if folks cannot start using that version
> artifacts immediately.
>
> See "Wait for about a day for the artifacts to show up in apache mirror
> (releases, public group) and maven central (mvnrepository.com or maven.org
> )."
> in the release process wiki.
>
> --
> Divij Vaidya
>
>
>
> On Tue, Feb 27, 2024 at 4:43 PM Stanislav Kozlovski
>  wrote:
>
> > Hey all,
> >
> > Everything site-related is merged.
> >
> > I have been following the final steps of the release process.
> > - Docker contains the release -
> https://hub.docker.com/r/apache/kafka/tags
> > - Maven central contains the release -
> >
> >
> https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13/3.7.0/versions
> > .
> > Note it says Feb 9 publish date, but it was just published. The RC4 files
> > were created on Feb 9 though, so I assume that's why it says that
> > - mvnrepository is NOT yet up to date -
> > https://mvnrepository.com/artifact/org.apache.kafka/kafka-clients and
> > https://mvnrepository.com/artifact/org.apache.kafka/kafka
> >
> > Am I free to announce the release, or should I wait more for
> MVNRepository
> > to get up to date? For what it's worth, I "Released" the files 24 hours
> ago
> >
> > On Mon, Feb 26, 2024 at 10:42 AM Stanislav Kozlovski <
> > stanis...@confluent.io>
> > wrote:
> >
> > >
> > > This vote passes with *10 +1 votes* (3 bindings) and no 0 or -1 votes.
> > >
> > > +1 votes
> > >
> > > PMC Members (binding):
> > > * Mickael Maison
> > > * Justine Olshan
> > > * Divij Vaidya
> > >
> > > Community (non-binding):
> > > * Proven Provenzano
> > > * Federico Valeri
> > > * Vedarth Sharma
> > > * Andrew Schofield
> > > * Paolo Patierno
> > > * Jakub Scholz
> > > * Josep Prat
> > >
> > > 
> > >
> > > 0 votes
> > >
> > > * No votes
> > >
> > > 
> > >
> > > -1 votes
> > >
> > > * No votes
> > >
> > > 
> > >
> > > Vote thread:
> > > https://lists.apache.org/thread/71djwz292y2lzgwzm7n6n8o7x56zbgh9
> > >
> > > I'll continue with the release process and the release announcement
> will
> > > follow ASAP.
> > >
> > > Best,
> > > Stanislav
> > >
> > > On Sun, Feb 25, 2024 at 7:08 PM Mickael Maison <
> mickael.mai...@gmail.com
> > >
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> Thanks for sorting out the docs issues.
> > >> +1 (binding)
> > >>
> > >> Mickael
> > >>
> > >> On Fri, Feb 23, 2024 at 11:50 AM Stanislav Kozlovski
> > >>  wrote:
> > >> >
> > >> > Some quick updates:
> > >> >
> > >> > There were some inconsistencies between the documentation in the
> > >> > apache/kafka repo and the one in kafka-site. The process is such
> that
> > >> the
> > >> > apache/kafka docs are the source of truth, but we had a few
> > divergences
> > >> in
> > >> > the other repo. I have worked on correcting those with:
> > >> > - MINOR: Reconcile upgrade.html with kafka-site/36's version
> > >> >  and cherry-picked it
> > into
> > >> the
> > >> > 3.6 and 3.7 branches too
> > >> >
> > >> > Additionally, the 3.7 upgrade notes have been merged in
> apache/kafka -
> > >> MINOR:
> > >> > Add 3.7 upgrade notes <
> > https://github.com/apache/kafka/pull/15407/files
> > >> >.
> > >> >
> > >> > With that, I have opened a PR to move them to the kafka-site
> > repository
> > >> -
> > >> > https://github.com/apache/kafka-site/pull/587. That is awaiting
> > review.
> > >> >
> > >> > Similarly, the 3.7 blog post is ready for review again
> > >> >  and awaiting a
> review
> > >> on 37:
> > >> > Update default docs to point to the 3.7.0 release docs
> > >> > 
> > >> >
> > >> > I also have a WIP for fixing the 3.6 docs in the kafka-site repo
> > >> > . This isn't really
> > >> related
> > >> > to the release, but it's good to do.
> > >> >
> > >> > On Wed, Feb 21, 2024 at 4:55 AM Luke Chen 
> wrote:
> > >> >
> > >> > > Hi all,
> > >> > >
> > >> > > I found there is a bug (KAFKA-16283
> > >> > > ) in the
> > built-in
> > >> > > `RoundRobinPartitioner`, and it will cause only half of the
> > partitions
> > >> > > receiving the records. (I'm surprised our tests didn't catch it!?)
> > >> > > After further testing, I found this issue already existed in
> v3.0.0.
> > >> (I
> > >> > > didn't test 2.x versions)
> > >> > > I think this should not be a blocker to v3.7.0 since it's been
> there
> > >> for
> > >> > >

Re: [VOTE] 3.7.0 RC4

2024-02-27 Thread Divij Vaidya

We wait before making the announcement. The rationale is that there is not
much point announcing a release if folks cannot start using that version
artifacts immediately.

See "Wait for about a day for the artifacts to show up in apache mirror
(releases, public group) and maven central (mvnrepository.com or maven.org)."
in the release process wiki.

--
Divij Vaidya



On Tue, Feb 27, 2024 at 4:43 PM Stanislav Kozlovski
 wrote:

> Hey all,
>
> Everything site-related is merged.
>
> I have been following the final steps of the release process.
> - Docker contains the release - https://hub.docker.com/r/apache/kafka/tags
> - Maven central contains the release -
>
> https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13/3.7.0/versions
> .
> Note it says Feb 9 publish date, but it was just published. The RC4 files
> were created on Feb 9 though, so I assume that's why it says that
> - mvnrepository is NOT yet up to date -
> https://mvnrepository.com/artifact/org.apache.kafka/kafka-clients and
> https://mvnrepository.com/artifact/org.apache.kafka/kafka
>
> Am I free to announce the release, or should I wait more for MVNRepository
> to get up to date? For what it's worth, I "Released" the files 24 hours ago
>
> On Mon, Feb 26, 2024 at 10:42 AM Stanislav Kozlovski <
> stanis...@confluent.io>
> wrote:
>
> >
> > This vote passes with *10 +1 votes* (3 bindings) and no 0 or -1 votes.
> >
> > +1 votes
> >
> > PMC Members (binding):
> > * Mickael Maison
> > * Justine Olshan
> > * Divij Vaidya
> >
> > Community (non-binding):
> > * Proven Provenzano
> > * Federico Valeri
> > * Vedarth Sharma
> > * Andrew Schofield
> > * Paolo Patierno
> > * Jakub Scholz
> > * Josep Prat
> >
> > 
> >
> > 0 votes
> >
> > * No votes
> >
> > 
> >
> > -1 votes
> >
> > * No votes
> >
> > 
> >
> > Vote thread:
> > https://lists.apache.org/thread/71djwz292y2lzgwzm7n6n8o7x56zbgh9
> >
> > I'll continue with the release process and the release announcement will
> > follow ASAP.
> >
> > Best,
> > Stanislav
> >
> > On Sun, Feb 25, 2024 at 7:08 PM Mickael Maison  >
> > wrote:
> >
> >> Hi,
> >>
> >> Thanks for sorting out the docs issues.
> >> +1 (binding)
> >>
> >> Mickael
> >>
> >> On Fri, Feb 23, 2024 at 11:50 AM Stanislav Kozlovski
> >>  wrote:
> >> >
> >> > Some quick updates:
> >> >
> >> > There were some inconsistencies between the documentation in the
> >> > apache/kafka repo and the one in kafka-site. The process is such that
> >> the
> >> > apache/kafka docs are the source of truth, but we had a few
> divergences
> >> in
> >> > the other repo. I have worked on correcting those with:
> >> > - MINOR: Reconcile upgrade.html with kafka-site/36's version
> >> >  and cherry-picked it
> into
> >> the
> >> > 3.6 and 3.7 branches too
> >> >
> >> > Additionally, the 3.7 upgrade notes have been merged in apache/kafka -
> >> MINOR:
> >> > Add 3.7 upgrade notes <
> https://github.com/apache/kafka/pull/15407/files
> >> >.
> >> >
> >> > With that, I have opened a PR to move them to the kafka-site
> repository
> >> -
> >> > https://github.com/apache/kafka-site/pull/587. That is awaiting
> review.
> >> >
> >> > Similarly, the 3.7 blog post is ready for review again
> >> >  and awaiting a review
> >> on 37:
> >> > Update default docs to point to the 3.7.0 release docs
> >> > 
> >> >
> >> > I also have a WIP for fixing the 3.6 docs in the kafka-site repo
> >> > . This isn't really
> >> related
> >> > to the release, but it's good to do.
> >> >
> >> > On Wed, Feb 21, 2024 at 4:55 AM Luke Chen  wrote:
> >> >
> >> > > Hi all,
> >> > >
> >> > > I found there is a bug (KAFKA-16283
> >> > > ) in the
> built-in
> >> > > `RoundRobinPartitioner`, and it will cause only half of the
> partitions
> >> > > receiving the records. (I'm surprised our tests didn't catch it!?)
> >> > > After further testing, I found this issue already existed in v3.0.0.
> >> (I
> >> > > didn't test 2.x versions)
> >> > > I think this should not be a blocker to v3.7.0 since it's been there
> >> for
> >> > > years.
> >> > > But I think we should, at least, document it to notify users about
> >> this
> >> > > known issue.
> >> > > I've created 2 PRs to document it:
> >> > > https://github.com/apache/kafka/pull/15400
> >> > > https://github.com/apache/kafka-site/pull/585
> >> > >
> >> > > Let me know what you think.
> >> > >
> >> > > Thanks.
> >> > > Luke
> >> > >
> >> > > On Wed, Feb 21, 2024 at 10:52 AM Proven Provenzano
> >> > >  wrote:
> >> > >
> >> > > > HI,
> >> > > >
> >> > > > I've downloaded, built from source and then validated JBOD with
> >> KRaft
> >> > > works
> >> > > > along with migrating a cluster with JBOD from ZK to KRaft works.
> >> > > >
> >> > > > +1 (nonbinding) from me.
> >> > > >
> >> > > > --Proven
> >> > > >
> >> > > >

Re: [VOTE] 3.7.0 RC4

2024-02-27 Thread Stanislav Kozlovski

Hey all,

Everything site-related is merged.

I have been following the final steps of the release process.
- Docker contains the release - https://hub.docker.com/r/apache/kafka/tags
- Maven central contains the release -
https://central.sonatype.com/artifact/org.apache.kafka/kafka_2.13/3.7.0/versions.
Note it says Feb 9 publish date, but it was just published. The RC4 files
were created on Feb 9 though, so I assume that's why it says that
- mvnrepository is NOT yet up to date -
https://mvnrepository.com/artifact/org.apache.kafka/kafka-clients and
https://mvnrepository.com/artifact/org.apache.kafka/kafka

Am I free to announce the release, or should I wait more for MVNRepository
to get up to date? For what it's worth, I "Released" the files 24 hours ago

On Mon, Feb 26, 2024 at 10:42 AM Stanislav Kozlovski 
wrote:

>
> This vote passes with *10 +1 votes* (3 bindings) and no 0 or -1 votes.
>
> +1 votes
>
> PMC Members (binding):
> * Mickael Maison
> * Justine Olshan
> * Divij Vaidya
>
> Community (non-binding):
> * Proven Provenzano
> * Federico Valeri
> * Vedarth Sharma
> * Andrew Schofield
> * Paolo Patierno
> * Jakub Scholz
> * Josep Prat
>
> 
>
> 0 votes
>
> * No votes
>
> 
>
> -1 votes
>
> * No votes
>
> 
>
> Vote thread:
> https://lists.apache.org/thread/71djwz292y2lzgwzm7n6n8o7x56zbgh9
>
> I'll continue with the release process and the release announcement will
> follow ASAP.
>
> Best,
> Stanislav
>
> On Sun, Feb 25, 2024 at 7:08 PM Mickael Maison 
> wrote:
>
>> Hi,
>>
>> Thanks for sorting out the docs issues.
>> +1 (binding)
>>
>> Mickael
>>
>> On Fri, Feb 23, 2024 at 11:50 AM Stanislav Kozlovski
>>  wrote:
>> >
>> > Some quick updates:
>> >
>> > There were some inconsistencies between the documentation in the
>> > apache/kafka repo and the one in kafka-site. The process is such that
>> the
>> > apache/kafka docs are the source of truth, but we had a few divergences
>> in
>> > the other repo. I have worked on correcting those with:
>> > - MINOR: Reconcile upgrade.html with kafka-site/36's version
>> >  and cherry-picked it into
>> the
>> > 3.6 and 3.7 branches too
>> >
>> > Additionally, the 3.7 upgrade notes have been merged in apache/kafka -
>> MINOR:
>> > Add 3.7 upgrade notes > >.
>> >
>> > With that, I have opened a PR to move them to the kafka-site repository
>> -
>> > https://github.com/apache/kafka-site/pull/587. That is awaiting review.
>> >
>> > Similarly, the 3.7 blog post is ready for review again
>> >  and awaiting a review
>> on 37:
>> > Update default docs to point to the 3.7.0 release docs
>> > 
>> >
>> > I also have a WIP for fixing the 3.6 docs in the kafka-site repo
>> > . This isn't really
>> related
>> > to the release, but it's good to do.
>> >
>> > On Wed, Feb 21, 2024 at 4:55 AM Luke Chen  wrote:
>> >
>> > > Hi all,
>> > >
>> > > I found there is a bug (KAFKA-16283
>> > > ) in the built-in
>> > > `RoundRobinPartitioner`, and it will cause only half of the partitions
>> > > receiving the records. (I'm surprised our tests didn't catch it!?)
>> > > After further testing, I found this issue already existed in v3.0.0.
>> (I
>> > > didn't test 2.x versions)
>> > > I think this should not be a blocker to v3.7.0 since it's been there
>> for
>> > > years.
>> > > But I think we should, at least, document it to notify users about
>> this
>> > > known issue.
>> > > I've created 2 PRs to document it:
>> > > https://github.com/apache/kafka/pull/15400
>> > > https://github.com/apache/kafka-site/pull/585
>> > >
>> > > Let me know what you think.
>> > >
>> > > Thanks.
>> > > Luke
>> > >
>> > > On Wed, Feb 21, 2024 at 10:52 AM Proven Provenzano
>> > >  wrote:
>> > >
>> > > > HI,
>> > > >
>> > > > I've downloaded, built from source and then validated JBOD with
>> KRaft
>> > > works
>> > > > along with migrating a cluster with JBOD from ZK to KRaft works.
>> > > >
>> > > > +1 (nonbinding) from me.
>> > > >
>> > > > --Proven
>> > > >
>> > > > On Tue, Feb 20, 2024 at 2:13 PM Justine Olshan
>> > > > 
>> > > > wrote:
>> > > >
>> > > > > Hey folks,
>> > > > >
>> > > > > I've done the following to validate the release:
>> > > > >
>> > > > > -- validated the keys for all the artifacts
>> > > > > -- built from source and started a ZK cluster -- ran a few
>> workloads on
>> > > > it.
>> > > > > -- ran 2.12 Kraft cluster and ran a few workloads on it
>> > > > >
>> > > > > I see there is a lot of ongoing discussion about the upgrade
>> notes. +1
>> > > > > (binding) from me given Mickael is voting +1 as well.
>> > > > >
>> > > > > Justine
>> > > > >
>> > > > > On Tue, Feb 20, 2024 at 6:18 AM Divij Vaidya <
>> divijvaidy...@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > > I am a bit unclear on the precise

Re: [VOTE] 3.7.0 RC4

2024-02-26 Thread Stanislav Kozlovski

*(double-sending this to kafka-clients & users, as I forgot initially)*

This vote passes with *10 +1 votes* (3 bindings) and no 0 or -1 votes.

+1 votes

PMC Members (binding):
* Mickael Maison
* Justine Olshan
* Divij Vaidya

Community (non-binding):
* Proven Provenzano
* Federico Valeri
* Vedarth Sharma
* Andrew Schofield
* Paolo Patierno
* Jakub Scholz
* Josep Prat



0 votes

* No votes



-1 votes

* No votes



Vote thread:
https://lists.apache.org/thread/71djwz292y2lzgwzm7n6n8o7x56zbgh9

I'll continue with the release process and the release announcement will
follow ASAP.

On Mon, Feb 26, 2024 at 10:42 AM Stanislav Kozlovski 
wrote:

>
> This vote passes with *10 +1 votes* (3 bindings) and no 0 or -1 votes.
>
> +1 votes
>
> PMC Members (binding):
> * Mickael Maison
> * Justine Olshan
> * Divij Vaidya
>
> Community (non-binding):
> * Proven Provenzano
> * Federico Valeri
> * Vedarth Sharma
> * Andrew Schofield
> * Paolo Patierno
> * Jakub Scholz
> * Josep Prat
>
> 
>
> 0 votes
>
> * No votes
>
> 
>
> -1 votes
>
> * No votes
>
> 
>
> Vote thread:
> https://lists.apache.org/thread/71djwz292y2lzgwzm7n6n8o7x56zbgh9
>
> I'll continue with the release process and the release announcement will
> follow ASAP.
>
> Best,
> Stanislav
>
> On Sun, Feb 25, 2024 at 7:08 PM Mickael Maison 
> wrote:
>
>> Hi,
>>
>> Thanks for sorting out the docs issues.
>> +1 (binding)
>>
>> Mickael
>>
>> On Fri, Feb 23, 2024 at 11:50 AM Stanislav Kozlovski
>>  wrote:
>> >
>> > Some quick updates:
>> >
>> > There were some inconsistencies between the documentation in the
>> > apache/kafka repo and the one in kafka-site. The process is such that
>> the
>> > apache/kafka docs are the source of truth, but we had a few divergences
>> in
>> > the other repo. I have worked on correcting those with:
>> > - MINOR: Reconcile upgrade.html with kafka-site/36's version
>> >  and cherry-picked it into
>> the
>> > 3.6 and 3.7 branches too
>> >
>> > Additionally, the 3.7 upgrade notes have been merged in apache/kafka -
>> MINOR:
>> > Add 3.7 upgrade notes > >.
>> >
>> > With that, I have opened a PR to move them to the kafka-site repository
>> -
>> > https://github.com/apache/kafka-site/pull/587. That is awaiting review.
>> >
>> > Similarly, the 3.7 blog post is ready for review again
>> >  and awaiting a review
>> on 37:
>> > Update default docs to point to the 3.7.0 release docs
>> > 
>> >
>> > I also have a WIP for fixing the 3.6 docs in the kafka-site repo
>> > . This isn't really
>> related
>> > to the release, but it's good to do.
>> >
>> > On Wed, Feb 21, 2024 at 4:55 AM Luke Chen  wrote:
>> >
>> > > Hi all,
>> > >
>> > > I found there is a bug (KAFKA-16283
>> > > ) in the built-in
>> > > `RoundRobinPartitioner`, and it will cause only half of the partitions
>> > > receiving the records. (I'm surprised our tests didn't catch it!?)
>> > > After further testing, I found this issue already existed in v3.0.0.
>> (I
>> > > didn't test 2.x versions)
>> > > I think this should not be a blocker to v3.7.0 since it's been there
>> for
>> > > years.
>> > > But I think we should, at least, document it to notify users about
>> this
>> > > known issue.
>> > > I've created 2 PRs to document it:
>> > > https://github.com/apache/kafka/pull/15400
>> > > https://github.com/apache/kafka-site/pull/585
>> > >
>> > > Let me know what you think.
>> > >
>> > > Thanks.
>> > > Luke
>> > >
>> > > On Wed, Feb 21, 2024 at 10:52 AM Proven Provenzano
>> > >  wrote:
>> > >
>> > > > HI,
>> > > >
>> > > > I've downloaded, built from source and then validated JBOD with
>> KRaft
>> > > works
>> > > > along with migrating a cluster with JBOD from ZK to KRaft works.
>> > > >
>> > > > +1 (nonbinding) from me.
>> > > >
>> > > > --Proven
>> > > >
>> > > > On Tue, Feb 20, 2024 at 2:13 PM Justine Olshan
>> > > > 
>> > > > wrote:
>> > > >
>> > > > > Hey folks,
>> > > > >
>> > > > > I've done the following to validate the release:
>> > > > >
>> > > > > -- validated the keys for all the artifacts
>> > > > > -- built from source and started a ZK cluster -- ran a few
>> workloads on
>> > > > it.
>> > > > > -- ran 2.12 Kraft cluster and ran a few workloads on it
>> > > > >
>> > > > > I see there is a lot of ongoing discussion about the upgrade
>> notes. +1
>> > > > > (binding) from me given Mickael is voting +1 as well.
>> > > > >
>> > > > > Justine
>> > > > >
>> > > > > On Tue, Feb 20, 2024 at 6:18 AM Divij Vaidya <
>> divijvaidy...@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > > I am a bit unclear on the precise process regarding what
>> parts of
>> > > > this
>> > > > > > get merged at what time, and whether the release first needs to
>> be
>> > > done
>> > > > > or
>> > >

Re: [VOTE] 3.7.0 RC4

2024-02-26 Thread Stanislav Kozlovski

This vote passes with *10 +1 votes* (3 bindings) and no 0 or -1 votes.

+1 votes

PMC Members (binding):
* Mickael Maison
* Justine Olshan
* Divij Vaidya

Community (non-binding):
* Proven Provenzano
* Federico Valeri
* Vedarth Sharma
* Andrew Schofield
* Paolo Patierno
* Jakub Scholz
* Josep Prat



0 votes

* No votes



-1 votes

* No votes



Vote thread:
https://lists.apache.org/thread/71djwz292y2lzgwzm7n6n8o7x56zbgh9

I'll continue with the release process and the release announcement will
follow ASAP.

Best,
Stanislav

On Sun, Feb 25, 2024 at 7:08 PM Mickael Maison 
wrote:

> Hi,
>
> Thanks for sorting out the docs issues.
> +1 (binding)
>
> Mickael
>
> On Fri, Feb 23, 2024 at 11:50 AM Stanislav Kozlovski
>  wrote:
> >
> > Some quick updates:
> >
> > There were some inconsistencies between the documentation in the
> > apache/kafka repo and the one in kafka-site. The process is such that the
> > apache/kafka docs are the source of truth, but we had a few divergences
> in
> > the other repo. I have worked on correcting those with:
> > - MINOR: Reconcile upgrade.html with kafka-site/36's version
> >  and cherry-picked it into
> the
> > 3.6 and 3.7 branches too
> >
> > Additionally, the 3.7 upgrade notes have been merged in apache/kafka -
> MINOR:
> > Add 3.7 upgrade notes  >.
> >
> > With that, I have opened a PR to move them to the kafka-site repository -
> > https://github.com/apache/kafka-site/pull/587. That is awaiting review.
> >
> > Similarly, the 3.7 blog post is ready for review again
> >  and awaiting a review
> on 37:
> > Update default docs to point to the 3.7.0 release docs
> > 
> >
> > I also have a WIP for fixing the 3.6 docs in the kafka-site repo
> > . This isn't really
> related
> > to the release, but it's good to do.
> >
> > On Wed, Feb 21, 2024 at 4:55 AM Luke Chen  wrote:
> >
> > > Hi all,
> > >
> > > I found there is a bug (KAFKA-16283
> > > ) in the built-in
> > > `RoundRobinPartitioner`, and it will cause only half of the partitions
> > > receiving the records. (I'm surprised our tests didn't catch it!?)
> > > After further testing, I found this issue already existed in v3.0.0. (I
> > > didn't test 2.x versions)
> > > I think this should not be a blocker to v3.7.0 since it's been there
> for
> > > years.
> > > But I think we should, at least, document it to notify users about this
> > > known issue.
> > > I've created 2 PRs to document it:
> > > https://github.com/apache/kafka/pull/15400
> > > https://github.com/apache/kafka-site/pull/585
> > >
> > > Let me know what you think.
> > >
> > > Thanks.
> > > Luke
> > >
> > > On Wed, Feb 21, 2024 at 10:52 AM Proven Provenzano
> > >  wrote:
> > >
> > > > HI,
> > > >
> > > > I've downloaded, built from source and then validated JBOD with KRaft
> > > works
> > > > along with migrating a cluster with JBOD from ZK to KRaft works.
> > > >
> > > > +1 (nonbinding) from me.
> > > >
> > > > --Proven
> > > >
> > > > On Tue, Feb 20, 2024 at 2:13 PM Justine Olshan
> > > > 
> > > > wrote:
> > > >
> > > > > Hey folks,
> > > > >
> > > > > I've done the following to validate the release:
> > > > >
> > > > > -- validated the keys for all the artifacts
> > > > > -- built from source and started a ZK cluster -- ran a few
> workloads on
> > > > it.
> > > > > -- ran 2.12 Kraft cluster and ran a few workloads on it
> > > > >
> > > > > I see there is a lot of ongoing discussion about the upgrade
> notes. +1
> > > > > (binding) from me given Mickael is voting +1 as well.
> > > > >
> > > > > Justine
> > > > >
> > > > > On Tue, Feb 20, 2024 at 6:18 AM Divij Vaidya <
> divijvaidy...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > > I am a bit unclear on the precise process regarding what parts
> of
> > > > this
> > > > > > get merged at what time, and whether the release first needs to
> be
> > > done
> > > > > or
> > > > > > not.
> > > > > >
> > > > > > The order is as follows:
> > > > > >
> > > > > > 1. Release approved as part of this vote. After this we follow
> the
> > > > > > steps from here:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Process#ReleaseProcess-Afterthevotepasses
> > > > > >
> > > > > > 2. Upload artifacts to maven etc. These artifacts do not have RC
> > > suffix
> > > > > in
> > > > > > them. You need a PMC member to mark these artifacts as
> "production"
> > > in
> > > > > > apache svn.
> > > > > > 3. Update website changes (docs, blog etc.). This is where your
> PRs
> > > > > > on kafka-site repo get merged.
> > > > > > 4. Send a release announcement by email.
> > > > > >
> > > > > > --
> > > > > > Divij Vaidya
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Feb 20, 2024

Re: [VOTE] 3.7.0 RC4

2024-02-25 Thread Mickael Maison

Hi,

Thanks for sorting out the docs issues.
+1 (binding)

Mickael

On Fri, Feb 23, 2024 at 11:50 AM Stanislav Kozlovski
 wrote:
>
> Some quick updates:
>
> There were some inconsistencies between the documentation in the
> apache/kafka repo and the one in kafka-site. The process is such that the
> apache/kafka docs are the source of truth, but we had a few divergences in
> the other repo. I have worked on correcting those with:
> - MINOR: Reconcile upgrade.html with kafka-site/36's version
>  and cherry-picked it into the
> 3.6 and 3.7 branches too
>
> Additionally, the 3.7 upgrade notes have been merged in apache/kafka - MINOR:
> Add 3.7 upgrade notes .
>
> With that, I have opened a PR to move them to the kafka-site repository -
> https://github.com/apache/kafka-site/pull/587. That is awaiting review.
>
> Similarly, the 3.7 blog post is ready for review again
>  and awaiting a review on 37:
> Update default docs to point to the 3.7.0 release docs
> 
>
> I also have a WIP for fixing the 3.6 docs in the kafka-site repo
> . This isn't really related
> to the release, but it's good to do.
>
> On Wed, Feb 21, 2024 at 4:55 AM Luke Chen  wrote:
>
> > Hi all,
> >
> > I found there is a bug (KAFKA-16283
> > ) in the built-in
> > `RoundRobinPartitioner`, and it will cause only half of the partitions
> > receiving the records. (I'm surprised our tests didn't catch it!?)
> > After further testing, I found this issue already existed in v3.0.0. (I
> > didn't test 2.x versions)
> > I think this should not be a blocker to v3.7.0 since it's been there for
> > years.
> > But I think we should, at least, document it to notify users about this
> > known issue.
> > I've created 2 PRs to document it:
> > https://github.com/apache/kafka/pull/15400
> > https://github.com/apache/kafka-site/pull/585
> >
> > Let me know what you think.
> >
> > Thanks.
> > Luke
> >
> > On Wed, Feb 21, 2024 at 10:52 AM Proven Provenzano
> >  wrote:
> >
> > > HI,
> > >
> > > I've downloaded, built from source and then validated JBOD with KRaft
> > works
> > > along with migrating a cluster with JBOD from ZK to KRaft works.
> > >
> > > +1 (nonbinding) from me.
> > >
> > > --Proven
> > >
> > > On Tue, Feb 20, 2024 at 2:13 PM Justine Olshan
> > > 
> > > wrote:
> > >
> > > > Hey folks,
> > > >
> > > > I've done the following to validate the release:
> > > >
> > > > -- validated the keys for all the artifacts
> > > > -- built from source and started a ZK cluster -- ran a few workloads on
> > > it.
> > > > -- ran 2.12 Kraft cluster and ran a few workloads on it
> > > >
> > > > I see there is a lot of ongoing discussion about the upgrade notes. +1
> > > > (binding) from me given Mickael is voting +1 as well.
> > > >
> > > > Justine
> > > >
> > > > On Tue, Feb 20, 2024 at 6:18 AM Divij Vaidya 
> > > > wrote:
> > > >
> > > > > > I am a bit unclear on the precise process regarding what parts of
> > > this
> > > > > get merged at what time, and whether the release first needs to be
> > done
> > > > or
> > > > > not.
> > > > >
> > > > > The order is as follows:
> > > > >
> > > > > 1. Release approved as part of this vote. After this we follow the
> > > > > steps from here:
> > > > >
> > > > >
> > > >
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Process#ReleaseProcess-Afterthevotepasses
> > > > >
> > > > > 2. Upload artifacts to maven etc. These artifacts do not have RC
> > suffix
> > > > in
> > > > > them. You need a PMC member to mark these artifacts as "production"
> > in
> > > > > apache svn.
> > > > > 3. Update website changes (docs, blog etc.). This is where your PRs
> > > > > on kafka-site repo get merged.
> > > > > 4. Send a release announcement by email.
> > > > >
> > > > > --
> > > > > Divij Vaidya
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Feb 20, 2024 at 3:02 PM Stanislav Kozlovski
> > > > >  wrote:
> > > > >
> > > > > > Thanks for testing the release! And thanks for the review on the
> > > > > > documentation. Good catch on the license too.
> > > > > >
> > > > > > I have addressed the comments in the blog PR, and opened a few
> > other
> > > > PRs
> > > > > to
> > > > > > the website in relation to the release.
> > > > > >
> > > > > > - 37: Add download section for the latest 3.7 release
> > > > > > 
> > > > > > - 37: Update default docs to point to the 3.7.0 release docs
> > > > > > 
> > > > > > - 3.7: Add blog post for Kafka 3.7
> > > > > > 
> > > > > > - MINOR: Update stale upgrade_3_6_0 header links in documentation
> > > > > > 
> > > > > > - 37:

Re: [VOTE] 3.7.0 RC4

2024-02-23 Thread Stanislav Kozlovski

Some quick updates:

There were some inconsistencies between the documentation in the
apache/kafka repo and the one in kafka-site. The process is such that the
apache/kafka docs are the source of truth, but we had a few divergences in
the other repo. I have worked on correcting those with:
- MINOR: Reconcile upgrade.html with kafka-site/36's version
 and cherry-picked it into the
3.6 and 3.7 branches too

Additionally, the 3.7 upgrade notes have been merged in apache/kafka - MINOR:
Add 3.7 upgrade notes .

With that, I have opened a PR to move them to the kafka-site repository -
https://github.com/apache/kafka-site/pull/587. That is awaiting review.

Similarly, the 3.7 blog post is ready for review again
 and awaiting a review on 37:
Update default docs to point to the 3.7.0 release docs


I also have a WIP for fixing the 3.6 docs in the kafka-site repo
. This isn't really related
to the release, but it's good to do.

On Wed, Feb 21, 2024 at 4:55 AM Luke Chen  wrote:

> Hi all,
>
> I found there is a bug (KAFKA-16283
> ) in the built-in
> `RoundRobinPartitioner`, and it will cause only half of the partitions
> receiving the records. (I'm surprised our tests didn't catch it!?)
> After further testing, I found this issue already existed in v3.0.0. (I
> didn't test 2.x versions)
> I think this should not be a blocker to v3.7.0 since it's been there for
> years.
> But I think we should, at least, document it to notify users about this
> known issue.
> I've created 2 PRs to document it:
> https://github.com/apache/kafka/pull/15400
> https://github.com/apache/kafka-site/pull/585
>
> Let me know what you think.
>
> Thanks.
> Luke
>
> On Wed, Feb 21, 2024 at 10:52 AM Proven Provenzano
>  wrote:
>
> > HI,
> >
> > I've downloaded, built from source and then validated JBOD with KRaft
> works
> > along with migrating a cluster with JBOD from ZK to KRaft works.
> >
> > +1 (nonbinding) from me.
> >
> > --Proven
> >
> > On Tue, Feb 20, 2024 at 2:13 PM Justine Olshan
> > 
> > wrote:
> >
> > > Hey folks,
> > >
> > > I've done the following to validate the release:
> > >
> > > -- validated the keys for all the artifacts
> > > -- built from source and started a ZK cluster -- ran a few workloads on
> > it.
> > > -- ran 2.12 Kraft cluster and ran a few workloads on it
> > >
> > > I see there is a lot of ongoing discussion about the upgrade notes. +1
> > > (binding) from me given Mickael is voting +1 as well.
> > >
> > > Justine
> > >
> > > On Tue, Feb 20, 2024 at 6:18 AM Divij Vaidya 
> > > wrote:
> > >
> > > > > I am a bit unclear on the precise process regarding what parts of
> > this
> > > > get merged at what time, and whether the release first needs to be
> done
> > > or
> > > > not.
> > > >
> > > > The order is as follows:
> > > >
> > > > 1. Release approved as part of this vote. After this we follow the
> > > > steps from here:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Process#ReleaseProcess-Afterthevotepasses
> > > >
> > > > 2. Upload artifacts to maven etc. These artifacts do not have RC
> suffix
> > > in
> > > > them. You need a PMC member to mark these artifacts as "production"
> in
> > > > apache svn.
> > > > 3. Update website changes (docs, blog etc.). This is where your PRs
> > > > on kafka-site repo get merged.
> > > > 4. Send a release announcement by email.
> > > >
> > > > --
> > > > Divij Vaidya
> > > >
> > > >
> > > >
> > > > On Tue, Feb 20, 2024 at 3:02 PM Stanislav Kozlovski
> > > >  wrote:
> > > >
> > > > > Thanks for testing the release! And thanks for the review on the
> > > > > documentation. Good catch on the license too.
> > > > >
> > > > > I have addressed the comments in the blog PR, and opened a few
> other
> > > PRs
> > > > to
> > > > > the website in relation to the release.
> > > > >
> > > > > - 37: Add download section for the latest 3.7 release
> > > > > 
> > > > > - 37: Update default docs to point to the 3.7.0 release docs
> > > > > 
> > > > > - 3.7: Add blog post for Kafka 3.7
> > > > > 
> > > > > - MINOR: Update stale upgrade_3_6_0 header links in documentation
> > > > > 
> > > > > - 37: Add upgrade notes for the 3.7.0 release
> > > > > 
> > > > >
> > > > > I am a bit unclear on the precise process regarding what parts of
> > this
> > > > get
> > > > > merged at what time, and whether the release first needs to be done
> > or
> > > > not.
> > > > >
> > > > > Best,
> > > > > Stanislav
> > > > >
> > > > > On Mon, Feb 19, 2024 at

Re: [VOTE] 3.7.0 RC4

2024-02-20 Thread Luke Chen

Hi all,

I found there is a bug (KAFKA-16283
) in the built-in
`RoundRobinPartitioner`, and it will cause only half of the partitions
receiving the records. (I'm surprised our tests didn't catch it!?)
After further testing, I found this issue already existed in v3.0.0. (I
didn't test 2.x versions)
I think this should not be a blocker to v3.7.0 since it's been there for
years.
But I think we should, at least, document it to notify users about this
known issue.
I've created 2 PRs to document it:
https://github.com/apache/kafka/pull/15400
https://github.com/apache/kafka-site/pull/585

Let me know what you think.

Thanks.
Luke

On Wed, Feb 21, 2024 at 10:52 AM Proven Provenzano
 wrote:

> HI,
>
> I've downloaded, built from source and then validated JBOD with KRaft works
> along with migrating a cluster with JBOD from ZK to KRaft works.
>
> +1 (nonbinding) from me.
>
> --Proven
>
> On Tue, Feb 20, 2024 at 2:13 PM Justine Olshan
> 
> wrote:
>
> > Hey folks,
> >
> > I've done the following to validate the release:
> >
> > -- validated the keys for all the artifacts
> > -- built from source and started a ZK cluster -- ran a few workloads on
> it.
> > -- ran 2.12 Kraft cluster and ran a few workloads on it
> >
> > I see there is a lot of ongoing discussion about the upgrade notes. +1
> > (binding) from me given Mickael is voting +1 as well.
> >
> > Justine
> >
> > On Tue, Feb 20, 2024 at 6:18 AM Divij Vaidya 
> > wrote:
> >
> > > > I am a bit unclear on the precise process regarding what parts of
> this
> > > get merged at what time, and whether the release first needs to be done
> > or
> > > not.
> > >
> > > The order is as follows:
> > >
> > > 1. Release approved as part of this vote. After this we follow the
> > > steps from here:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Process#ReleaseProcess-Afterthevotepasses
> > >
> > > 2. Upload artifacts to maven etc. These artifacts do not have RC suffix
> > in
> > > them. You need a PMC member to mark these artifacts as "production" in
> > > apache svn.
> > > 3. Update website changes (docs, blog etc.). This is where your PRs
> > > on kafka-site repo get merged.
> > > 4. Send a release announcement by email.
> > >
> > > --
> > > Divij Vaidya
> > >
> > >
> > >
> > > On Tue, Feb 20, 2024 at 3:02 PM Stanislav Kozlovski
> > >  wrote:
> > >
> > > > Thanks for testing the release! And thanks for the review on the
> > > > documentation. Good catch on the license too.
> > > >
> > > > I have addressed the comments in the blog PR, and opened a few other
> > PRs
> > > to
> > > > the website in relation to the release.
> > > >
> > > > - 37: Add download section for the latest 3.7 release
> > > > 
> > > > - 37: Update default docs to point to the 3.7.0 release docs
> > > > 
> > > > - 3.7: Add blog post for Kafka 3.7
> > > > 
> > > > - MINOR: Update stale upgrade_3_6_0 header links in documentation
> > > > 
> > > > - 37: Add upgrade notes for the 3.7.0 release
> > > > 
> > > >
> > > > I am a bit unclear on the precise process regarding what parts of
> this
> > > get
> > > > merged at what time, and whether the release first needs to be done
> or
> > > not.
> > > >
> > > > Best,
> > > > Stanislav
> > > >
> > > > On Mon, Feb 19, 2024 at 8:34 PM Divij Vaidya <
> divijvaidy...@gmail.com>
> > > > wrote:
> > > >
> > > > > Great. In that case we can fix the license issue retrospectively. I
> > > have
> > > > > created a JIRA for it
> > > https://issues.apache.org/jira/browse/KAFKA-16278
> > > > > and
> > > > > also updated the release process (which redirects to
> > > > > https://issues.apache.org/jira/browse/KAFKA-12622) to check for
> the
> > > > > correct
> > > > > license in both the kafka binaries.
> > > > >
> > > > > I am +1 (binding) assuming Mickael's concerns about update notes to
> > 3.7
> > > > are
> > > > > addressed before release.
> > > > >
> > > > > --
> > > > > Divij Vaidya
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Feb 19, 2024 at 6:08 PM Mickael Maison <
> > > mickael.mai...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I agree with Josep, I don't think it's worth making a new RC just
> > for
> > > > > this.
> > > > > >
> > > > > > Thanks Stanislav for sharing the test results. The last thing
> > holding
> > > > > > me from casting my vote is the missing upgrade notes for 3.7.0.
> > > > > >
> > > > > > Thanks,
> > > > > > Mickael
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, Feb 19, 2024 at 4:28 PM Josep Prat
> > >  > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > I think I remember finding a similar problem (NOTICE_binary)
> and
> > it
> > > > > > didn't
> > > > > > > qualify for an extra

Re: [VOTE] 3.7.0 RC4

2024-02-20 Thread Proven Provenzano

HI,

I've downloaded, built from source and then validated JBOD with KRaft works
along with migrating a cluster with JBOD from ZK to KRaft works.

+1 (nonbinding) from me.

--Proven

On Tue, Feb 20, 2024 at 2:13 PM Justine Olshan 
wrote:

> Hey folks,
>
> I've done the following to validate the release:
>
> -- validated the keys for all the artifacts
> -- built from source and started a ZK cluster -- ran a few workloads on it.
> -- ran 2.12 Kraft cluster and ran a few workloads on it
>
> I see there is a lot of ongoing discussion about the upgrade notes. +1
> (binding) from me given Mickael is voting +1 as well.
>
> Justine
>
> On Tue, Feb 20, 2024 at 6:18 AM Divij Vaidya 
> wrote:
>
> > > I am a bit unclear on the precise process regarding what parts of this
> > get merged at what time, and whether the release first needs to be done
> or
> > not.
> >
> > The order is as follows:
> >
> > 1. Release approved as part of this vote. After this we follow the
> > steps from here:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Process#ReleaseProcess-Afterthevotepasses
> >
> > 2. Upload artifacts to maven etc. These artifacts do not have RC suffix
> in
> > them. You need a PMC member to mark these artifacts as "production" in
> > apache svn.
> > 3. Update website changes (docs, blog etc.). This is where your PRs
> > on kafka-site repo get merged.
> > 4. Send a release announcement by email.
> >
> > --
> > Divij Vaidya
> >
> >
> >
> > On Tue, Feb 20, 2024 at 3:02 PM Stanislav Kozlovski
> >  wrote:
> >
> > > Thanks for testing the release! And thanks for the review on the
> > > documentation. Good catch on the license too.
> > >
> > > I have addressed the comments in the blog PR, and opened a few other
> PRs
> > to
> > > the website in relation to the release.
> > >
> > > - 37: Add download section for the latest 3.7 release
> > > 
> > > - 37: Update default docs to point to the 3.7.0 release docs
> > > 
> > > - 3.7: Add blog post for Kafka 3.7
> > > 
> > > - MINOR: Update stale upgrade_3_6_0 header links in documentation
> > > 
> > > - 37: Add upgrade notes for the 3.7.0 release
> > > 
> > >
> > > I am a bit unclear on the precise process regarding what parts of this
> > get
> > > merged at what time, and whether the release first needs to be done or
> > not.
> > >
> > > Best,
> > > Stanislav
> > >
> > > On Mon, Feb 19, 2024 at 8:34 PM Divij Vaidya 
> > > wrote:
> > >
> > > > Great. In that case we can fix the license issue retrospectively. I
> > have
> > > > created a JIRA for it
> > https://issues.apache.org/jira/browse/KAFKA-16278
> > > > and
> > > > also updated the release process (which redirects to
> > > > https://issues.apache.org/jira/browse/KAFKA-12622) to check for the
> > > > correct
> > > > license in both the kafka binaries.
> > > >
> > > > I am +1 (binding) assuming Mickael's concerns about update notes to
> 3.7
> > > are
> > > > addressed before release.
> > > >
> > > > --
> > > > Divij Vaidya
> > > >
> > > >
> > > >
> > > > On Mon, Feb 19, 2024 at 6:08 PM Mickael Maison <
> > mickael.mai...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I agree with Josep, I don't think it's worth making a new RC just
> for
> > > > this.
> > > > >
> > > > > Thanks Stanislav for sharing the test results. The last thing
> holding
> > > > > me from casting my vote is the missing upgrade notes for 3.7.0.
> > > > >
> > > > > Thanks,
> > > > > Mickael
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Feb 19, 2024 at 4:28 PM Josep Prat
> >  > > >
> > > > > wrote:
> > > > > >
> > > > > > I think I remember finding a similar problem (NOTICE_binary) and
> it
> > > > > didn't
> > > > > > qualify for an extra RC
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > On Mon, Feb 19, 2024 at 3:44 PM Divij Vaidya <
> > > divijvaidy...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > I have performed the following checks. The only thing I would
> > like
> > > to
> > > > > call
> > > > > > > out is the missing licenses before providing a vote. How do we
> > want
> > > > > > > to proceed on this? What have we done in the past? (Creating a
> > new
> > > RC
> > > > > is
> > > > > > > overkill IMO for this license issue).
> > > > > > >
> > > > > > > ## License check
> > > > > > >
> > > > > > > Test: Validate license of dependencies for both 2.12 & 2.13
> > binary.
> > > > > > > Result: Missing license for some scala* libraries specifically
> > for
> > > > > 2.12.
> > > > > > > Seems like we have been missing these licenses for quite some
> > > version
> > > > > now.
> > > > > > >
> > > > > > > ```
> > > > > > > for f in $(ls libs | grep -v "^kafka\|connect\|trogdor"); do
> if !
> > > > grep
> > > > > -q
> > > > > > > ${f%.*} LICENSE; then echo

Re: [VOTE] 3.7.0 RC4

2024-02-20 Thread Justine Olshan

Hey folks,

I've done the following to validate the release:

-- validated the keys for all the artifacts
-- built from source and started a ZK cluster -- ran a few workloads on it.
-- ran 2.12 Kraft cluster and ran a few workloads on it

I see there is a lot of ongoing discussion about the upgrade notes. +1
(binding) from me given Mickael is voting +1 as well.

Justine

On Tue, Feb 20, 2024 at 6:18 AM Divij Vaidya 
wrote:

> > I am a bit unclear on the precise process regarding what parts of this
> get merged at what time, and whether the release first needs to be done or
> not.
>
> The order is as follows:
>
> 1. Release approved as part of this vote. After this we follow the
> steps from here:
>
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Process#ReleaseProcess-Afterthevotepasses
>
> 2. Upload artifacts to maven etc. These artifacts do not have RC suffix in
> them. You need a PMC member to mark these artifacts as "production" in
> apache svn.
> 3. Update website changes (docs, blog etc.). This is where your PRs
> on kafka-site repo get merged.
> 4. Send a release announcement by email.
>
> --
> Divij Vaidya
>
>
>
> On Tue, Feb 20, 2024 at 3:02 PM Stanislav Kozlovski
>  wrote:
>
> > Thanks for testing the release! And thanks for the review on the
> > documentation. Good catch on the license too.
> >
> > I have addressed the comments in the blog PR, and opened a few other PRs
> to
> > the website in relation to the release.
> >
> > - 37: Add download section for the latest 3.7 release
> > 
> > - 37: Update default docs to point to the 3.7.0 release docs
> > 
> > - 3.7: Add blog post for Kafka 3.7
> > 
> > - MINOR: Update stale upgrade_3_6_0 header links in documentation
> > 
> > - 37: Add upgrade notes for the 3.7.0 release
> > 
> >
> > I am a bit unclear on the precise process regarding what parts of this
> get
> > merged at what time, and whether the release first needs to be done or
> not.
> >
> > Best,
> > Stanislav
> >
> > On Mon, Feb 19, 2024 at 8:34 PM Divij Vaidya 
> > wrote:
> >
> > > Great. In that case we can fix the license issue retrospectively. I
> have
> > > created a JIRA for it
> https://issues.apache.org/jira/browse/KAFKA-16278
> > > and
> > > also updated the release process (which redirects to
> > > https://issues.apache.org/jira/browse/KAFKA-12622) to check for the
> > > correct
> > > license in both the kafka binaries.
> > >
> > > I am +1 (binding) assuming Mickael's concerns about update notes to 3.7
> > are
> > > addressed before release.
> > >
> > > --
> > > Divij Vaidya
> > >
> > >
> > >
> > > On Mon, Feb 19, 2024 at 6:08 PM Mickael Maison <
> mickael.mai...@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I agree with Josep, I don't think it's worth making a new RC just for
> > > this.
> > > >
> > > > Thanks Stanislav for sharing the test results. The last thing holding
> > > > me from casting my vote is the missing upgrade notes for 3.7.0.
> > > >
> > > > Thanks,
> > > > Mickael
> > > >
> > > >
> > > >
> > > > On Mon, Feb 19, 2024 at 4:28 PM Josep Prat
>  > >
> > > > wrote:
> > > > >
> > > > > I think I remember finding a similar problem (NOTICE_binary) and it
> > > > didn't
> > > > > qualify for an extra RC
> > > > >
> > > > > Best,
> > > > >
> > > > > On Mon, Feb 19, 2024 at 3:44 PM Divij Vaidya <
> > divijvaidy...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > I have performed the following checks. The only thing I would
> like
> > to
> > > > call
> > > > > > out is the missing licenses before providing a vote. How do we
> want
> > > > > > to proceed on this? What have we done in the past? (Creating a
> new
> > RC
> > > > is
> > > > > > overkill IMO for this license issue).
> > > > > >
> > > > > > ## License check
> > > > > >
> > > > > > Test: Validate license of dependencies for both 2.12 & 2.13
> binary.
> > > > > > Result: Missing license for some scala* libraries specifically
> for
> > > > 2.12.
> > > > > > Seems like we have been missing these licenses for quite some
> > version
> > > > now.
> > > > > >
> > > > > > ```
> > > > > > for f in $(ls libs | grep -v "^kafka\|connect\|trogdor"); do if !
> > > grep
> > > > -q
> > > > > > ${f%.*} LICENSE; then echo "${f%.*} is missing in license file";
> > fi;
> > > > done
> > > > > > scala-collection-compat_2.12-2.10.0 is missing in license file
> > > > > > scala-java8-compat_2.12-1.0.2 is missing in license file
> > > > > > scala-library-2.12.18 is missing in license file
> > > > > > scala-logging_2.12-3.9.4 is missing in license file
> > > > > > scala-reflect-2.12.18 is missing in license file
> > > > > > ```
> > > > > >
> > > > > > ## Long running tests for memory leak (on ARM machine with zstd)
> > > > > >
> > > > > > Test: Run produce/consume for a few

Re: [VOTE] 3.7.0 RC4

2024-02-20 Thread Divij Vaidya

> I am a bit unclear on the precise process regarding what parts of this
get merged at what time, and whether the release first needs to be done or
not.

The order is as follows:

1. Release approved as part of this vote. After this we follow the
steps from here:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Process#ReleaseProcess-Afterthevotepasses

2. Upload artifacts to maven etc. These artifacts do not have RC suffix in
them. You need a PMC member to mark these artifacts as "production" in
apache svn.
3. Update website changes (docs, blog etc.). This is where your PRs
on kafka-site repo get merged.
4. Send a release announcement by email.

--
Divij Vaidya



On Tue, Feb 20, 2024 at 3:02 PM Stanislav Kozlovski
 wrote:

> Thanks for testing the release! And thanks for the review on the
> documentation. Good catch on the license too.
>
> I have addressed the comments in the blog PR, and opened a few other PRs to
> the website in relation to the release.
>
> - 37: Add download section for the latest 3.7 release
> 
> - 37: Update default docs to point to the 3.7.0 release docs
> 
> - 3.7: Add blog post for Kafka 3.7
> 
> - MINOR: Update stale upgrade_3_6_0 header links in documentation
> 
> - 37: Add upgrade notes for the 3.7.0 release
> 
>
> I am a bit unclear on the precise process regarding what parts of this get
> merged at what time, and whether the release first needs to be done or not.
>
> Best,
> Stanislav
>
> On Mon, Feb 19, 2024 at 8:34 PM Divij Vaidya 
> wrote:
>
> > Great. In that case we can fix the license issue retrospectively. I have
> > created a JIRA for it https://issues.apache.org/jira/browse/KAFKA-16278
> > and
> > also updated the release process (which redirects to
> > https://issues.apache.org/jira/browse/KAFKA-12622) to check for the
> > correct
> > license in both the kafka binaries.
> >
> > I am +1 (binding) assuming Mickael's concerns about update notes to 3.7
> are
> > addressed before release.
> >
> > --
> > Divij Vaidya
> >
> >
> >
> > On Mon, Feb 19, 2024 at 6:08 PM Mickael Maison  >
> > wrote:
> >
> > > Hi,
> > >
> > > I agree with Josep, I don't think it's worth making a new RC just for
> > this.
> > >
> > > Thanks Stanislav for sharing the test results. The last thing holding
> > > me from casting my vote is the missing upgrade notes for 3.7.0.
> > >
> > > Thanks,
> > > Mickael
> > >
> > >
> > >
> > > On Mon, Feb 19, 2024 at 4:28 PM Josep Prat  >
> > > wrote:
> > > >
> > > > I think I remember finding a similar problem (NOTICE_binary) and it
> > > didn't
> > > > qualify for an extra RC
> > > >
> > > > Best,
> > > >
> > > > On Mon, Feb 19, 2024 at 3:44 PM Divij Vaidya <
> divijvaidy...@gmail.com>
> > > > wrote:
> > > >
> > > > > I have performed the following checks. The only thing I would like
> to
> > > call
> > > > > out is the missing licenses before providing a vote. How do we want
> > > > > to proceed on this? What have we done in the past? (Creating a new
> RC
> > > is
> > > > > overkill IMO for this license issue).
> > > > >
> > > > > ## License check
> > > > >
> > > > > Test: Validate license of dependencies for both 2.12 & 2.13 binary.
> > > > > Result: Missing license for some scala* libraries specifically for
> > > 2.12.
> > > > > Seems like we have been missing these licenses for quite some
> version
> > > now.
> > > > >
> > > > > ```
> > > > > for f in $(ls libs | grep -v "^kafka\|connect\|trogdor"); do if !
> > grep
> > > -q
> > > > > ${f%.*} LICENSE; then echo "${f%.*} is missing in license file";
> fi;
> > > done
> > > > > scala-collection-compat_2.12-2.10.0 is missing in license file
> > > > > scala-java8-compat_2.12-1.0.2 is missing in license file
> > > > > scala-library-2.12.18 is missing in license file
> > > > > scala-logging_2.12-3.9.4 is missing in license file
> > > > > scala-reflect-2.12.18 is missing in license file
> > > > > ```
> > > > >
> > > > > ## Long running tests for memory leak (on ARM machine with zstd)
> > > > >
> > > > > Test: Run produce/consume for a few hours and verify no gradual
> > > increase in
> > > > > heap.
> > > > > Result: No heap increase observed. The overall CPU utilization is
> > lower
> > > > > compared to 3.5.1.
> > > > >
> > > > > ## Verify system test results
> > > > >
> > > > > Test: Spot check the results of system tests.
> > > > > Result: I have verified that the system tests are passing across
> > > different
> > > > > runs.
> > > > >
> > > > > --
> > > > > Divij Vaidya
> > > > >
> > > > >
> > > > >
> > > > > On Sun, Feb 18, 2024 at 2:50 PM Stanislav Kozlovski
> > > > >  wrote:
> > > > >
> > > > > > The latest system test build completed successfully -
> > > > > >
> > > > > >
> > > > >
> > >
> >
>

Re: [VOTE] 3.7.0 RC4

2024-02-20 Thread Stanislav Kozlovski

Thanks for testing the release! And thanks for the review on the
documentation. Good catch on the license too.

I have addressed the comments in the blog PR, and opened a few other PRs to
the website in relation to the release.

- 37: Add download section for the latest 3.7 release

- 37: Update default docs to point to the 3.7.0 release docs

- 3.7: Add blog post for Kafka 3.7

- MINOR: Update stale upgrade_3_6_0 header links in documentation

- 37: Add upgrade notes for the 3.7.0 release


I am a bit unclear on the precise process regarding what parts of this get
merged at what time, and whether the release first needs to be done or not.

Best,
Stanislav

On Mon, Feb 19, 2024 at 8:34 PM Divij Vaidya 
wrote:

> Great. In that case we can fix the license issue retrospectively. I have
> created a JIRA for it https://issues.apache.org/jira/browse/KAFKA-16278
> and
> also updated the release process (which redirects to
> https://issues.apache.org/jira/browse/KAFKA-12622) to check for the
> correct
> license in both the kafka binaries.
>
> I am +1 (binding) assuming Mickael's concerns about update notes to 3.7 are
> addressed before release.
>
> --
> Divij Vaidya
>
>
>
> On Mon, Feb 19, 2024 at 6:08 PM Mickael Maison 
> wrote:
>
> > Hi,
> >
> > I agree with Josep, I don't think it's worth making a new RC just for
> this.
> >
> > Thanks Stanislav for sharing the test results. The last thing holding
> > me from casting my vote is the missing upgrade notes for 3.7.0.
> >
> > Thanks,
> > Mickael
> >
> >
> >
> > On Mon, Feb 19, 2024 at 4:28 PM Josep Prat 
> > wrote:
> > >
> > > I think I remember finding a similar problem (NOTICE_binary) and it
> > didn't
> > > qualify for an extra RC
> > >
> > > Best,
> > >
> > > On Mon, Feb 19, 2024 at 3:44 PM Divij Vaidya 
> > > wrote:
> > >
> > > > I have performed the following checks. The only thing I would like to
> > call
> > > > out is the missing licenses before providing a vote. How do we want
> > > > to proceed on this? What have we done in the past? (Creating a new RC
> > is
> > > > overkill IMO for this license issue).
> > > >
> > > > ## License check
> > > >
> > > > Test: Validate license of dependencies for both 2.12 & 2.13 binary.
> > > > Result: Missing license for some scala* libraries specifically for
> > 2.12.
> > > > Seems like we have been missing these licenses for quite some version
> > now.
> > > >
> > > > ```
> > > > for f in $(ls libs | grep -v "^kafka\|connect\|trogdor"); do if !
> grep
> > -q
> > > > ${f%.*} LICENSE; then echo "${f%.*} is missing in license file"; fi;
> > done
> > > > scala-collection-compat_2.12-2.10.0 is missing in license file
> > > > scala-java8-compat_2.12-1.0.2 is missing in license file
> > > > scala-library-2.12.18 is missing in license file
> > > > scala-logging_2.12-3.9.4 is missing in license file
> > > > scala-reflect-2.12.18 is missing in license file
> > > > ```
> > > >
> > > > ## Long running tests for memory leak (on ARM machine with zstd)
> > > >
> > > > Test: Run produce/consume for a few hours and verify no gradual
> > increase in
> > > > heap.
> > > > Result: No heap increase observed. The overall CPU utilization is
> lower
> > > > compared to 3.5.1.
> > > >
> > > > ## Verify system test results
> > > >
> > > > Test: Spot check the results of system tests.
> > > > Result: I have verified that the system tests are passing across
> > different
> > > > runs.
> > > >
> > > > --
> > > > Divij Vaidya
> > > >
> > > >
> > > >
> > > > On Sun, Feb 18, 2024 at 2:50 PM Stanislav Kozlovski
> > > >  wrote:
> > > >
> > > > > The latest system test build completed successfully -
> > > > >
> > > > >
> > > >
> >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708250728--apache--3.7--02197edaaa/2024-02-18--001./2024-02-18--001./report.html
> > > > >
> > > > > *System tests are therefore all good*. We just have some flakes
> > > > >
> > > > > On Sun, Feb 18, 2024 at 10:45 AM Stanislav Kozlovski <
> > > > > stanis...@confluent.io>
> > > > > wrote:
> > > > >
> > > > > > The upgrade test passed ->
> > > > > >
> > > > >
> > > >
> >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708103771--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
> > > > > >
> > > > > > The replica verification test succeeded in ZK mode, but failed in
> > > > > > ISOLATED_KRAFT. It just seems to be very flaky.
> > > > > >
> > > > >
> > > >
> >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708100119--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
> > > > > >
> >

Re: [VOTE] 3.7.0 RC4

2024-02-19 Thread Divij Vaidya

Great. In that case we can fix the license issue retrospectively. I have
created a JIRA for it https://issues.apache.org/jira/browse/KAFKA-16278 and
also updated the release process (which redirects to
https://issues.apache.org/jira/browse/KAFKA-12622) to check for the correct
license in both the kafka binaries.

I am +1 (binding) assuming Mickael's concerns about update notes to 3.7 are
addressed before release.

--
Divij Vaidya



On Mon, Feb 19, 2024 at 6:08 PM Mickael Maison 
wrote:

> Hi,
>
> I agree with Josep, I don't think it's worth making a new RC just for this.
>
> Thanks Stanislav for sharing the test results. The last thing holding
> me from casting my vote is the missing upgrade notes for 3.7.0.
>
> Thanks,
> Mickael
>
>
>
> On Mon, Feb 19, 2024 at 4:28 PM Josep Prat 
> wrote:
> >
> > I think I remember finding a similar problem (NOTICE_binary) and it
> didn't
> > qualify for an extra RC
> >
> > Best,
> >
> > On Mon, Feb 19, 2024 at 3:44 PM Divij Vaidya 
> > wrote:
> >
> > > I have performed the following checks. The only thing I would like to
> call
> > > out is the missing licenses before providing a vote. How do we want
> > > to proceed on this? What have we done in the past? (Creating a new RC
> is
> > > overkill IMO for this license issue).
> > >
> > > ## License check
> > >
> > > Test: Validate license of dependencies for both 2.12 & 2.13 binary.
> > > Result: Missing license for some scala* libraries specifically for
> 2.12.
> > > Seems like we have been missing these licenses for quite some version
> now.
> > >
> > > ```
> > > for f in $(ls libs | grep -v "^kafka\|connect\|trogdor"); do if ! grep
> -q
> > > ${f%.*} LICENSE; then echo "${f%.*} is missing in license file"; fi;
> done
> > > scala-collection-compat_2.12-2.10.0 is missing in license file
> > > scala-java8-compat_2.12-1.0.2 is missing in license file
> > > scala-library-2.12.18 is missing in license file
> > > scala-logging_2.12-3.9.4 is missing in license file
> > > scala-reflect-2.12.18 is missing in license file
> > > ```
> > >
> > > ## Long running tests for memory leak (on ARM machine with zstd)
> > >
> > > Test: Run produce/consume for a few hours and verify no gradual
> increase in
> > > heap.
> > > Result: No heap increase observed. The overall CPU utilization is lower
> > > compared to 3.5.1.
> > >
> > > ## Verify system test results
> > >
> > > Test: Spot check the results of system tests.
> > > Result: I have verified that the system tests are passing across
> different
> > > runs.
> > >
> > > --
> > > Divij Vaidya
> > >
> > >
> > >
> > > On Sun, Feb 18, 2024 at 2:50 PM Stanislav Kozlovski
> > >  wrote:
> > >
> > > > The latest system test build completed successfully -
> > > >
> > > >
> > >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708250728--apache--3.7--02197edaaa/2024-02-18--001./2024-02-18--001./report.html
> > > >
> > > > *System tests are therefore all good*. We just have some flakes
> > > >
> > > > On Sun, Feb 18, 2024 at 10:45 AM Stanislav Kozlovski <
> > > > stanis...@confluent.io>
> > > > wrote:
> > > >
> > > > > The upgrade test passed ->
> > > > >
> > > >
> > >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708103771--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
> > > > >
> > > > > The replica verification test succeeded in ZK mode, but failed in
> > > > > ISOLATED_KRAFT. It just seems to be very flaky.
> > > > >
> > > >
> > >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708100119--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
> > > > >
> > > > > Scheduling another run in
> > > > >
> > >
> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6062/
> > > > >
> > > > > On Fri, Feb 16, 2024 at 6:39 PM Stanislav Kozlovski <
> > > > > stanis...@confluent.io> wrote:
> > > > >
> > > > >> Thanks all for the help in verifying.
> > > > >>
> > > > >> I have updated
> > > > >>
> > > >
> > >
> https://gist.github.com/stanislavkozlovski/820976fc7bfb5f4dcdf9742fd96a9982
> > > > >> with the system tests.
> > > > >> There were two builds ran, and across those - the following tests
> > > failed
> > > > >> two times in a row:
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> *kafkatest.tests.tools.replica_verification_test.ReplicaVerificationToolTest#test_replica_lagsArguments:{
> > > > >> "metadata_quorum": "ZK"}*Fails with the same error of
> > > > >> *`TimeoutError('Timed out waiting to reach non-zero number of
> replica
> > > > >> lags.')`*
> > > > >> I have scheduled a re-run of this specific test here ->
> > > > >>
> > > https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6057
> > > > >>
> > > > >>
> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
> > > > >> "compression_types": [

Re: [VOTE] 3.7.0 RC4

2024-02-19 Thread Mickael Maison

Hi,

I agree with Josep, I don't think it's worth making a new RC just for this.

Thanks Stanislav for sharing the test results. The last thing holding
me from casting my vote is the missing upgrade notes for 3.7.0.

Thanks,
Mickael



On Mon, Feb 19, 2024 at 4:28 PM Josep Prat  wrote:
>
> I think I remember finding a similar problem (NOTICE_binary) and it didn't
> qualify for an extra RC
>
> Best,
>
> On Mon, Feb 19, 2024 at 3:44 PM Divij Vaidya 
> wrote:
>
> > I have performed the following checks. The only thing I would like to call
> > out is the missing licenses before providing a vote. How do we want
> > to proceed on this? What have we done in the past? (Creating a new RC is
> > overkill IMO for this license issue).
> >
> > ## License check
> >
> > Test: Validate license of dependencies for both 2.12 & 2.13 binary.
> > Result: Missing license for some scala* libraries specifically for 2.12.
> > Seems like we have been missing these licenses for quite some version now.
> >
> > ```
> > for f in $(ls libs | grep -v "^kafka\|connect\|trogdor"); do if ! grep -q
> > ${f%.*} LICENSE; then echo "${f%.*} is missing in license file"; fi; done
> > scala-collection-compat_2.12-2.10.0 is missing in license file
> > scala-java8-compat_2.12-1.0.2 is missing in license file
> > scala-library-2.12.18 is missing in license file
> > scala-logging_2.12-3.9.4 is missing in license file
> > scala-reflect-2.12.18 is missing in license file
> > ```
> >
> > ## Long running tests for memory leak (on ARM machine with zstd)
> >
> > Test: Run produce/consume for a few hours and verify no gradual increase in
> > heap.
> > Result: No heap increase observed. The overall CPU utilization is lower
> > compared to 3.5.1.
> >
> > ## Verify system test results
> >
> > Test: Spot check the results of system tests.
> > Result: I have verified that the system tests are passing across different
> > runs.
> >
> > --
> > Divij Vaidya
> >
> >
> >
> > On Sun, Feb 18, 2024 at 2:50 PM Stanislav Kozlovski
> >  wrote:
> >
> > > The latest system test build completed successfully -
> > >
> > >
> > https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708250728--apache--3.7--02197edaaa/2024-02-18--001./2024-02-18--001./report.html
> > >
> > > *System tests are therefore all good*. We just have some flakes
> > >
> > > On Sun, Feb 18, 2024 at 10:45 AM Stanislav Kozlovski <
> > > stanis...@confluent.io>
> > > wrote:
> > >
> > > > The upgrade test passed ->
> > > >
> > >
> > https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708103771--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
> > > >
> > > > The replica verification test succeeded in ZK mode, but failed in
> > > > ISOLATED_KRAFT. It just seems to be very flaky.
> > > >
> > >
> > https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708100119--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
> > > >
> > > > Scheduling another run in
> > > >
> > https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6062/
> > > >
> > > > On Fri, Feb 16, 2024 at 6:39 PM Stanislav Kozlovski <
> > > > stanis...@confluent.io> wrote:
> > > >
> > > >> Thanks all for the help in verifying.
> > > >>
> > > >> I have updated
> > > >>
> > >
> > https://gist.github.com/stanislavkozlovski/820976fc7bfb5f4dcdf9742fd96a9982
> > > >> with the system tests.
> > > >> There were two builds ran, and across those - the following tests
> > failed
> > > >> two times in a row:
> > > >>
> > > >>
> > > >>
> > >
> > *kafkatest.tests.tools.replica_verification_test.ReplicaVerificationToolTest#test_replica_lagsArguments:{
> > > >> "metadata_quorum": "ZK"}*Fails with the same error of
> > > >> *`TimeoutError('Timed out waiting to reach non-zero number of replica
> > > >> lags.')`*
> > > >> I have scheduled a re-run of this specific test here ->
> > > >>
> > https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6057
> > > >>
> > > >> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
> > > >> "compression_types": [ "zstd" ], "from_kafka_version": "2.4.1",
> > > >> "to_message_format_version": null}*
> > > >> Fails with the same error of
> > > >> *`TimeoutError('Producer failed to produce messages for 20s.')`*
> > > >> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
> > > >> "compression_types": [ "lz4" ], "from_kafka_version": "3.0.2",
> > > >> "to_message_format_version": null}*
> > > >> Fails with the same error of *`TimeoutError('Producer failed to
> > produce
> > > >> messages for 20s.')`*
> > > >>
> > > >> I have scheduled a re-run of this test here ->
> > > >>
> > https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6058/
> > > >>
> > > >> On Fri, Feb 16, 2024 at 12:15 PM Vedarth Sharma <
> > > vedarth.sha...@gmail.com>

Re: [VOTE] 3.7.0 RC4

2024-02-19 Thread Josep Prat

I think I remember finding a similar problem (NOTICE_binary) and it didn't
qualify for an extra RC

Best,

On Mon, Feb 19, 2024 at 3:44 PM Divij Vaidya 
wrote:

> I have performed the following checks. The only thing I would like to call
> out is the missing licenses before providing a vote. How do we want
> to proceed on this? What have we done in the past? (Creating a new RC is
> overkill IMO for this license issue).
>
> ## License check
>
> Test: Validate license of dependencies for both 2.12 & 2.13 binary.
> Result: Missing license for some scala* libraries specifically for 2.12.
> Seems like we have been missing these licenses for quite some version now.
>
> ```
> for f in $(ls libs | grep -v "^kafka\|connect\|trogdor"); do if ! grep -q
> ${f%.*} LICENSE; then echo "${f%.*} is missing in license file"; fi; done
> scala-collection-compat_2.12-2.10.0 is missing in license file
> scala-java8-compat_2.12-1.0.2 is missing in license file
> scala-library-2.12.18 is missing in license file
> scala-logging_2.12-3.9.4 is missing in license file
> scala-reflect-2.12.18 is missing in license file
> ```
>
> ## Long running tests for memory leak (on ARM machine with zstd)
>
> Test: Run produce/consume for a few hours and verify no gradual increase in
> heap.
> Result: No heap increase observed. The overall CPU utilization is lower
> compared to 3.5.1.
>
> ## Verify system test results
>
> Test: Spot check the results of system tests.
> Result: I have verified that the system tests are passing across different
> runs.
>
> --
> Divij Vaidya
>
>
>
> On Sun, Feb 18, 2024 at 2:50 PM Stanislav Kozlovski
>  wrote:
>
> > The latest system test build completed successfully -
> >
> >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708250728--apache--3.7--02197edaaa/2024-02-18--001./2024-02-18--001./report.html
> >
> > *System tests are therefore all good*. We just have some flakes
> >
> > On Sun, Feb 18, 2024 at 10:45 AM Stanislav Kozlovski <
> > stanis...@confluent.io>
> > wrote:
> >
> > > The upgrade test passed ->
> > >
> >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708103771--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
> > >
> > > The replica verification test succeeded in ZK mode, but failed in
> > > ISOLATED_KRAFT. It just seems to be very flaky.
> > >
> >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708100119--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
> > >
> > > Scheduling another run in
> > >
> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6062/
> > >
> > > On Fri, Feb 16, 2024 at 6:39 PM Stanislav Kozlovski <
> > > stanis...@confluent.io> wrote:
> > >
> > >> Thanks all for the help in verifying.
> > >>
> > >> I have updated
> > >>
> >
> https://gist.github.com/stanislavkozlovski/820976fc7bfb5f4dcdf9742fd96a9982
> > >> with the system tests.
> > >> There were two builds ran, and across those - the following tests
> failed
> > >> two times in a row:
> > >>
> > >>
> > >>
> >
> *kafkatest.tests.tools.replica_verification_test.ReplicaVerificationToolTest#test_replica_lagsArguments:{
> > >> "metadata_quorum": "ZK"}*Fails with the same error of
> > >> *`TimeoutError('Timed out waiting to reach non-zero number of replica
> > >> lags.')`*
> > >> I have scheduled a re-run of this specific test here ->
> > >>
> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6057
> > >>
> > >> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
> > >> "compression_types": [ "zstd" ], "from_kafka_version": "2.4.1",
> > >> "to_message_format_version": null}*
> > >> Fails with the same error of
> > >> *`TimeoutError('Producer failed to produce messages for 20s.')`*
> > >> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
> > >> "compression_types": [ "lz4" ], "from_kafka_version": "3.0.2",
> > >> "to_message_format_version": null}*
> > >> Fails with the same error of *`TimeoutError('Producer failed to
> produce
> > >> messages for 20s.')`*
> > >>
> > >> I have scheduled a re-run of this test here ->
> > >>
> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6058/
> > >>
> > >> On Fri, Feb 16, 2024 at 12:15 PM Vedarth Sharma <
> > vedarth.sha...@gmail.com>
> > >> wrote:
> > >>
> > >>> Hey Stanislav,
> > >>>
> > >>> Thanks for the release candidate.
> > >>>
> > >>> +1 (non-binding)
> > >>>
> > >>> I tested and verified the docker image artifact
> > apache/kafka:3.7.0-rc4:-
> > >>> - verified create topic, produce messages and consume messages flow
> > when
> > >>> running the docker image with
> > >>> - default configs
> > >>> - configs provided via env variables
> > >>> - configs provided via file input
> > >>> - verified the html documentation for docker

Re: [VOTE] 3.7.0 RC4

2024-02-19 Thread Divij Vaidya

I have performed the following checks. The only thing I would like to call
out is the missing licenses before providing a vote. How do we want
to proceed on this? What have we done in the past? (Creating a new RC is
overkill IMO for this license issue).

## License check

Test: Validate license of dependencies for both 2.12 & 2.13 binary.
Result: Missing license for some scala* libraries specifically for 2.12.
Seems like we have been missing these licenses for quite some version now.

```
for f in $(ls libs | grep -v "^kafka\|connect\|trogdor"); do if ! grep -q
${f%.*} LICENSE; then echo "${f%.*} is missing in license file"; fi; done
scala-collection-compat_2.12-2.10.0 is missing in license file
scala-java8-compat_2.12-1.0.2 is missing in license file
scala-library-2.12.18 is missing in license file
scala-logging_2.12-3.9.4 is missing in license file
scala-reflect-2.12.18 is missing in license file
```

## Long running tests for memory leak (on ARM machine with zstd)

Test: Run produce/consume for a few hours and verify no gradual increase in
heap.
Result: No heap increase observed. The overall CPU utilization is lower
compared to 3.5.1.

## Verify system test results

Test: Spot check the results of system tests.
Result: I have verified that the system tests are passing across different
runs.

--
Divij Vaidya



On Sun, Feb 18, 2024 at 2:50 PM Stanislav Kozlovski
 wrote:

> The latest system test build completed successfully -
>
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708250728--apache--3.7--02197edaaa/2024-02-18--001./2024-02-18--001./report.html
>
> *System tests are therefore all good*. We just have some flakes
>
> On Sun, Feb 18, 2024 at 10:45 AM Stanislav Kozlovski <
> stanis...@confluent.io>
> wrote:
>
> > The upgrade test passed ->
> >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708103771--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
> >
> > The replica verification test succeeded in ZK mode, but failed in
> > ISOLATED_KRAFT. It just seems to be very flaky.
> >
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708100119--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
> >
> > Scheduling another run in
> > https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6062/
> >
> > On Fri, Feb 16, 2024 at 6:39 PM Stanislav Kozlovski <
> > stanis...@confluent.io> wrote:
> >
> >> Thanks all for the help in verifying.
> >>
> >> I have updated
> >>
> https://gist.github.com/stanislavkozlovski/820976fc7bfb5f4dcdf9742fd96a9982
> >> with the system tests.
> >> There were two builds ran, and across those - the following tests failed
> >> two times in a row:
> >>
> >>
> >>
> *kafkatest.tests.tools.replica_verification_test.ReplicaVerificationToolTest#test_replica_lagsArguments:{
> >> "metadata_quorum": "ZK"}*Fails with the same error of
> >> *`TimeoutError('Timed out waiting to reach non-zero number of replica
> >> lags.')`*
> >> I have scheduled a re-run of this specific test here ->
> >> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6057
> >>
> >> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
> >> "compression_types": [ "zstd" ], "from_kafka_version": "2.4.1",
> >> "to_message_format_version": null}*
> >> Fails with the same error of
> >> *`TimeoutError('Producer failed to produce messages for 20s.')`*
> >> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
> >> "compression_types": [ "lz4" ], "from_kafka_version": "3.0.2",
> >> "to_message_format_version": null}*
> >> Fails with the same error of *`TimeoutError('Producer failed to produce
> >> messages for 20s.')`*
> >>
> >> I have scheduled a re-run of this test here ->
> >> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6058/
> >>
> >> On Fri, Feb 16, 2024 at 12:15 PM Vedarth Sharma <
> vedarth.sha...@gmail.com>
> >> wrote:
> >>
> >>> Hey Stanislav,
> >>>
> >>> Thanks for the release candidate.
> >>>
> >>> +1 (non-binding)
> >>>
> >>> I tested and verified the docker image artifact
> apache/kafka:3.7.0-rc4:-
> >>> - verified create topic, produce messages and consume messages flow
> when
> >>> running the docker image with
> >>> - default configs
> >>> - configs provided via env variables
> >>> - configs provided via file input
> >>> - verified the html documentation for docker image.
> >>> - ran the example docker compose files successfully.
> >>>
> >>> All looks good for the docker image artifact!
> >>>
> >>> Thanks and regards,
> >>> Vedarth
> >>>
> >>>
> >>> On Thu, Feb 15, 2024 at 10:58 PM Mickael Maison <
> >>> mickael.mai...@gmail.com>
> >>> wrote:
> >>>
> >>> > Hi Stanislav,
> >>> >
> >>> > Thanks for running the release.
> >>> >
> >>> > I did the following testing:
>

Re: [VOTE] 3.7.0 RC4

2024-02-18 Thread Stanislav Kozlovski

The latest system test build completed successfully -
https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708250728--apache--3.7--02197edaaa/2024-02-18--001./2024-02-18--001./report.html

*System tests are therefore all good*. We just have some flakes

On Sun, Feb 18, 2024 at 10:45 AM Stanislav Kozlovski 
wrote:

> The upgrade test passed ->
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708103771--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
>
> The replica verification test succeeded in ZK mode, but failed in
> ISOLATED_KRAFT. It just seems to be very flaky.
> https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708100119--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html
>
> Scheduling another run in
> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6062/
>
> On Fri, Feb 16, 2024 at 6:39 PM Stanislav Kozlovski <
> stanis...@confluent.io> wrote:
>
>> Thanks all for the help in verifying.
>>
>> I have updated
>> https://gist.github.com/stanislavkozlovski/820976fc7bfb5f4dcdf9742fd96a9982
>> with the system tests.
>> There were two builds ran, and across those - the following tests failed
>> two times in a row:
>>
>>
>> *kafkatest.tests.tools.replica_verification_test.ReplicaVerificationToolTest#test_replica_lagsArguments:{
>> "metadata_quorum": "ZK"}*Fails with the same error of
>> *`TimeoutError('Timed out waiting to reach non-zero number of replica
>> lags.')`*
>> I have scheduled a re-run of this specific test here ->
>> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6057
>>
>> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
>> "compression_types": [ "zstd" ], "from_kafka_version": "2.4.1",
>> "to_message_format_version": null}*
>> Fails with the same error of
>> *`TimeoutError('Producer failed to produce messages for 20s.')`*
>> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
>> "compression_types": [ "lz4" ], "from_kafka_version": "3.0.2",
>> "to_message_format_version": null}*
>> Fails with the same error of *`TimeoutError('Producer failed to produce
>> messages for 20s.')`*
>>
>> I have scheduled a re-run of this test here ->
>> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6058/
>>
>> On Fri, Feb 16, 2024 at 12:15 PM Vedarth Sharma 
>> wrote:
>>
>>> Hey Stanislav,
>>>
>>> Thanks for the release candidate.
>>>
>>> +1 (non-binding)
>>>
>>> I tested and verified the docker image artifact apache/kafka:3.7.0-rc4:-
>>> - verified create topic, produce messages and consume messages flow when
>>> running the docker image with
>>> - default configs
>>> - configs provided via env variables
>>> - configs provided via file input
>>> - verified the html documentation for docker image.
>>> - ran the example docker compose files successfully.
>>>
>>> All looks good for the docker image artifact!
>>>
>>> Thanks and regards,
>>> Vedarth
>>>
>>>
>>> On Thu, Feb 15, 2024 at 10:58 PM Mickael Maison <
>>> mickael.mai...@gmail.com>
>>> wrote:
>>>
>>> > Hi Stanislav,
>>> >
>>> > Thanks for running the release.
>>> >
>>> > I did the following testing:
>>> > - verified the check sums and signatures
>>> > - ran ZooKeeper and KRaft quickstarts with Scala 2.13 binaries
>>> > - ran a successful migration from ZooKeeper to KRaft
>>> >
>>> > We seem to be missing the upgrade notes for 3.7.0 in the docs. See
>>> > https://kafka.apache.org/37/documentation.html#upgrade that still
>>> > points to 3.6.0
>>> > Before voting I'd like to see results from the system tests too.
>>> >
>>> > Thanks,
>>> > Mickael
>>> >
>>> > On Thu, Feb 15, 2024 at 6:06 PM Andrew Schofield
>>> >  wrote:
>>> > >
>>> > > +1 (non-binding). I used the staged binaries with Scala 2.13. I tried
>>> > the new group coordinator
>>> > > and consumer group protocol which is included with the Early Access
>>> > release of KIP-848.
>>> > > Also verified the availability of the new APIs. All working as
>>> expected.
>>> > >
>>> > > Thanks,
>>> > > Andrew
>>> > >
>>> > > > On 15 Feb 2024, at 05:07, Paolo Patierno >> >
>>> > wrote:
>>> > > >
>>> > > > +1 (non-binding). I used the staged binaries with Scala 2.13 and
>>> mostly
>>> > > > focused on the ZooKeeper to KRaft migration with multiple tests.
>>> > Everything
>>> > > > works fine.
>>> > > >
>>> > > > Thanks
>>> > > > Paolo
>>> > > >
>>> > > > On Mon, 12 Feb 2024, 22:06 Jakub Scholz,  wrote:
>>> > > >
>>> > > >> +1 (non-binding). I used the staged binaries with Scala 2.13 and
>>> the
>>> > staged
>>> > > >> Maven artifacts to run my tests. All seems to work fine. Thanks.
>>> > > >>
>>> > > >> Jakub
>>> > > >>
>>> > > >> On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
>>> > > >>  wrote:
>>> > > >>
>>> > > >>> Hello Kafka users, developers and

Re: [VOTE] 3.7.0 RC4

2024-02-18 Thread Stanislav Kozlovski

The upgrade test passed ->
https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708103771--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html

The replica verification test succeeded in ZK mode, but failed in
ISOLATED_KRAFT. It just seems to be very flaky.
https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1708100119--apache--3.7--bb6990114b/2024-02-16--001./2024-02-16--001./report.html

Scheduling another run in
https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6062/

On Fri, Feb 16, 2024 at 6:39 PM Stanislav Kozlovski 
wrote:

> Thanks all for the help in verifying.
>
> I have updated
> https://gist.github.com/stanislavkozlovski/820976fc7bfb5f4dcdf9742fd96a9982
> with the system tests.
> There were two builds ran, and across those - the following tests failed
> two times in a row:
>
>
> *kafkatest.tests.tools.replica_verification_test.ReplicaVerificationToolTest#test_replica_lagsArguments:{
> "metadata_quorum": "ZK"}*Fails with the same error of
> *`TimeoutError('Timed out waiting to reach non-zero number of replica
> lags.')`*
> I have scheduled a re-run of this specific test here ->
> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6057
>
> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
> "compression_types": [ "zstd" ], "from_kafka_version": "2.4.1",
> "to_message_format_version": null}*
> Fails with the same error of
> *`TimeoutError('Producer failed to produce messages for 20s.')`*
> *kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
> "compression_types": [ "lz4" ], "from_kafka_version": "3.0.2",
> "to_message_format_version": null}*
> Fails with the same error of *`TimeoutError('Producer failed to produce
> messages for 20s.')`*
>
> I have scheduled a re-run of this test here ->
> https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6058/
>
> On Fri, Feb 16, 2024 at 12:15 PM Vedarth Sharma 
> wrote:
>
>> Hey Stanislav,
>>
>> Thanks for the release candidate.
>>
>> +1 (non-binding)
>>
>> I tested and verified the docker image artifact apache/kafka:3.7.0-rc4:-
>> - verified create topic, produce messages and consume messages flow when
>> running the docker image with
>> - default configs
>> - configs provided via env variables
>> - configs provided via file input
>> - verified the html documentation for docker image.
>> - ran the example docker compose files successfully.
>>
>> All looks good for the docker image artifact!
>>
>> Thanks and regards,
>> Vedarth
>>
>>
>> On Thu, Feb 15, 2024 at 10:58 PM Mickael Maison > >
>> wrote:
>>
>> > Hi Stanislav,
>> >
>> > Thanks for running the release.
>> >
>> > I did the following testing:
>> > - verified the check sums and signatures
>> > - ran ZooKeeper and KRaft quickstarts with Scala 2.13 binaries
>> > - ran a successful migration from ZooKeeper to KRaft
>> >
>> > We seem to be missing the upgrade notes for 3.7.0 in the docs. See
>> > https://kafka.apache.org/37/documentation.html#upgrade that still
>> > points to 3.6.0
>> > Before voting I'd like to see results from the system tests too.
>> >
>> > Thanks,
>> > Mickael
>> >
>> > On Thu, Feb 15, 2024 at 6:06 PM Andrew Schofield
>> >  wrote:
>> > >
>> > > +1 (non-binding). I used the staged binaries with Scala 2.13. I tried
>> > the new group coordinator
>> > > and consumer group protocol which is included with the Early Access
>> > release of KIP-848.
>> > > Also verified the availability of the new APIs. All working as
>> expected.
>> > >
>> > > Thanks,
>> > > Andrew
>> > >
>> > > > On 15 Feb 2024, at 05:07, Paolo Patierno 
>> > wrote:
>> > > >
>> > > > +1 (non-binding). I used the staged binaries with Scala 2.13 and
>> mostly
>> > > > focused on the ZooKeeper to KRaft migration with multiple tests.
>> > Everything
>> > > > works fine.
>> > > >
>> > > > Thanks
>> > > > Paolo
>> > > >
>> > > > On Mon, 12 Feb 2024, 22:06 Jakub Scholz,  wrote:
>> > > >
>> > > >> +1 (non-binding). I used the staged binaries with Scala 2.13 and
>> the
>> > staged
>> > > >> Maven artifacts to run my tests. All seems to work fine. Thanks.
>> > > >>
>> > > >> Jakub
>> > > >>
>> > > >> On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
>> > > >>  wrote:
>> > > >>
>> > > >>> Hello Kafka users, developers and client-developers,
>> > > >>>
>> > > >>> This is the second candidate we are considering for release of
>> Apache
>> > > >> Kafka
>> > > >>> 3.7.0.
>> > > >>>
>> > > >>> Major changes include:
>> > > >>> - Early Access to KIP-848 - the next generation of the consumer
>> > rebalance
>> > > >>> protocol
>> > > >>> - Early Access to KIP-858: Adding JBOD support to KRaft
>> > > >>> - KIP-714: Observability into Client metrics via a standardized
>> > interface
>> > > >>>
>> > > >>> Release notes for the 3.7.0 release:
>> > > >>>
>> > > >>>
>> > > >>
>> >
>>

Re: [VOTE] 3.7.0 RC4

2024-02-16 Thread Stanislav Kozlovski

Thanks all for the help in verifying.

I have updated
https://gist.github.com/stanislavkozlovski/820976fc7bfb5f4dcdf9742fd96a9982
with the system tests.
There were two builds ran, and across those - the following tests failed
two times in a row:


*kafkatest.tests.tools.replica_verification_test.ReplicaVerificationToolTest#test_replica_lagsArguments:{
"metadata_quorum": "ZK"}*Fails with the same error of
*`TimeoutError('Timed out waiting to reach non-zero number of replica
lags.')`*
I have scheduled a re-run of this specific test here ->
https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6057

*kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
"compression_types": [ "zstd" ], "from_kafka_version": "2.4.1",
"to_message_format_version": null}*
Fails with the same error of
*`TimeoutError('Producer failed to produce messages for 20s.')`*
*kafkatest.tests.core.upgrade_test.TestUpgrade#test_upgradeArguments:{
"compression_types": [ "lz4" ], "from_kafka_version": "3.0.2",
"to_message_format_version": null}*
Fails with the same error of *`TimeoutError('Producer failed to produce
messages for 20s.')`*

I have scheduled a re-run of this test here ->
https://jenkins.confluent.io/job/system-test-kafka-branch-builder/6058/

On Fri, Feb 16, 2024 at 12:15 PM Vedarth Sharma 
wrote:

> Hey Stanislav,
>
> Thanks for the release candidate.
>
> +1 (non-binding)
>
> I tested and verified the docker image artifact apache/kafka:3.7.0-rc4:-
> - verified create topic, produce messages and consume messages flow when
> running the docker image with
> - default configs
> - configs provided via env variables
> - configs provided via file input
> - verified the html documentation for docker image.
> - ran the example docker compose files successfully.
>
> All looks good for the docker image artifact!
>
> Thanks and regards,
> Vedarth
>
>
> On Thu, Feb 15, 2024 at 10:58 PM Mickael Maison 
> wrote:
>
> > Hi Stanislav,
> >
> > Thanks for running the release.
> >
> > I did the following testing:
> > - verified the check sums and signatures
> > - ran ZooKeeper and KRaft quickstarts with Scala 2.13 binaries
> > - ran a successful migration from ZooKeeper to KRaft
> >
> > We seem to be missing the upgrade notes for 3.7.0 in the docs. See
> > https://kafka.apache.org/37/documentation.html#upgrade that still
> > points to 3.6.0
> > Before voting I'd like to see results from the system tests too.
> >
> > Thanks,
> > Mickael
> >
> > On Thu, Feb 15, 2024 at 6:06 PM Andrew Schofield
> >  wrote:
> > >
> > > +1 (non-binding). I used the staged binaries with Scala 2.13. I tried
> > the new group coordinator
> > > and consumer group protocol which is included with the Early Access
> > release of KIP-848.
> > > Also verified the availability of the new APIs. All working as
> expected.
> > >
> > > Thanks,
> > > Andrew
> > >
> > > > On 15 Feb 2024, at 05:07, Paolo Patierno 
> > wrote:
> > > >
> > > > +1 (non-binding). I used the staged binaries with Scala 2.13 and
> mostly
> > > > focused on the ZooKeeper to KRaft migration with multiple tests.
> > Everything
> > > > works fine.
> > > >
> > > > Thanks
> > > > Paolo
> > > >
> > > > On Mon, 12 Feb 2024, 22:06 Jakub Scholz,  wrote:
> > > >
> > > >> +1 (non-binding). I used the staged binaries with Scala 2.13 and the
> > staged
> > > >> Maven artifacts to run my tests. All seems to work fine. Thanks.
> > > >>
> > > >> Jakub
> > > >>
> > > >> On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
> > > >>  wrote:
> > > >>
> > > >>> Hello Kafka users, developers and client-developers,
> > > >>>
> > > >>> This is the second candidate we are considering for release of
> Apache
> > > >> Kafka
> > > >>> 3.7.0.
> > > >>>
> > > >>> Major changes include:
> > > >>> - Early Access to KIP-848 - the next generation of the consumer
> > rebalance
> > > >>> protocol
> > > >>> - Early Access to KIP-858: Adding JBOD support to KRaft
> > > >>> - KIP-714: Observability into Client metrics via a standardized
> > interface
> > > >>>
> > > >>> Release notes for the 3.7.0 release:
> > > >>>
> > > >>>
> > > >>
> >
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
> > > >>>
> > > >>> *** Please download, test and vote by Thursday, February 15th, 9AM
> > PST
> > > >> ***
> > > >>>
> > > >>> 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/~stanislavkozlovski/kafka-3.7.0-rc4/
> > > >>>
> > > >>> * Docker release artifact to be voted upon:
> > > >>> apache/kafka:3.7.0-rc4
> > > >>>
> > > >>> * Maven artifacts to be voted upon:
> > > >>>
> > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > > >>>
> > > >>> * Javadoc:
> > > >>>
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/javadoc/
> > > >>>
> > > >>> * Tag to be voted upon (off 3.7 branch) is the 3.7.0 tag:

Re: [VOTE] 3.7.0 RC4

2024-02-16 Thread Federico Valeri

Hi Stanislav, it's +1 (non binding) for me.

- Built from source using Java 17 and Scala 2.13.
- Ran all unit and integration tests.
- Used the staged Maven artifacts to test some client applications
against ZK and KRaft based clusters.
- Tested the Cluster-wide dynamic log adjustment for Kafka Connect
with a 3 nodes cluster.
- Tried the new Docker image.
- Ran system tests (most failed tests are related to streams, see report below).

Thanks
Fede

---

### flaky

[INFO:2024-02-16 00:47:39,263]: RunnerClient: Loading test
{'directory': '/opt/kafka-dev/tests/kafkatest/tests/core',
'file_name': 'reassign_partitions_test.py', 'cls_name':
'ReassignPartitionsTest', 'method_name': 'test_reassign_partitions',
'injected_args': {'bounce_brokers': False, 'metadata_quorum':
'ISOLATED_KRAFT', 'reassign_from_offset_zero': False,
'use_new_coordinator': False}}

### failed (single tests)

[INFO:2024-02-15 23:18:38,332]: RunnerClient: Loading test
{'directory': '/opt/kafka-dev/tests/kafkatest/tests/core',
'file_name': 'downgrade_test.py', 'cls_name': 'TestDowngrade',
'method_name': 'test_upgrade_and_downgrade', 'injected_args':
{'compression_types': 'none', 'static_membership': True, 'version':
'2.8.2'}}

[INFO:2024-02-15 23:30:22,380]: RunnerClient: Loading test
{'directory': '/opt/kafka-dev/tests/kafkatest/tests/core',
'file_name': 'network_degrade_test.py', 'cls_name':
'NetworkDegradeTest', 'method_name': 'test_rate', 'injected_args':
{'device_name': 'eth0', 'latency_ms': 50, 'rate_limit_kbit': 100,
'task_name': 'rate-1000-latency-50'}}

[INFO:2024-02-16 05:44:00,934]: RunnerClient: Loading test
{'directory': '/opt/kafka-dev/tests/kafkatest/tests/streams',
'file_name': 'streams_upgrade_test.py', 'cls_name':
'StreamsUpgradeTest', 'method_name': 'test_version_probing_upgrade',
'injected_args': None}

# failed (14 tests with increasing from_version)

[INFO:2024-02-16 05:14:15,576]: RunnerClient: Loading test
{'directory': '/opt/kafka-dev/tests/kafkatest/tests/streams',
'file_name': 'streams_application_upgrade_test.py', 'cls_name':
'StreamsUpgradeTest', 'method_name': 'test_app_upgrade',
'injected_args': {'bounce_type': 'full', 'from_version': '2.2.2',
'to_version': '3.7.0-SNAPSHOT'}}

# failed (18 tests with increasing from_version)

[INFO:2024-02-16 05:37:08,823]: RunnerClient: Loading test
{'directory': '/opt/kafka-dev/tests/kafkatest/tests/streams',
'file_name': 'streams_upgrade_test.py', 'cls_name':
'StreamsUpgradeTest', 'method_name':
'test_rolling_upgrade_with_2_bounces', 'injected_args':
{'from_version': '0.10.0.1', 'to_version': '3.7.0-SNAPSHOT'}}

# failed (4 tests with increasing from_version)

[INFO:2024-02-16 05:41:10,539]: RunnerClient: Loading test
{'directory': '/opt/kafka-dev/tests/kafkatest/tests/streams',
'file_name': 'streams_upgrade_test.py', 'cls_name':
'StreamsUpgradeTest', 'method_name':
'test_upgrade_downgrade_state_updater', 'injected_args':
{'from_version': '3.2.3', 'to_version': '3.7.0-SNAPSHOT', 'upgrade':
False}}








On Thu, Feb 15, 2024 at 3:39 PM Andrew Schofield
 wrote:
>
> +1 (non-binding). I used the staged binaries with Scala 2.13. I tried the new 
> group coordinator
> and consumer group protocol which is included with the Early Access release 
> of KIP-848.
> Also verified the availability of the new APIs. All working as expected.
>
> Thanks,
> Andrew
>
> > On 15 Feb 2024, at 05:07, Paolo Patierno  wrote:
> >
> > +1 (non-binding). I used the staged binaries with Scala 2.13 and mostly
> > focused on the ZooKeeper to KRaft migration with multiple tests. Everything
> > works fine.
> >
> > Thanks
> > Paolo
> >
> > On Mon, 12 Feb 2024, 22:06 Jakub Scholz,  wrote:
> >
> >> +1 (non-binding). I used the staged binaries with Scala 2.13 and the staged
> >> Maven artifacts to run my tests. All seems to work fine. Thanks.
> >>
> >> Jakub
> >>
> >> On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
> >>  wrote:
> >>
> >>> Hello Kafka users, developers and client-developers,
> >>>
> >>> This is the second candidate we are considering for release of Apache
> >> Kafka
> >>> 3.7.0.
> >>>
> >>> Major changes include:
> >>> - Early Access to KIP-848 - the next generation of the consumer rebalance
> >>> protocol
> >>> - Early Access to KIP-858: Adding JBOD support to KRaft
> >>> - KIP-714: Observability into Client metrics via a standardized interface
> >>>
> >>> Release notes for the 3.7.0 release:
> >>>
> >>>
> >> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
> >>>
> >>> *** Please download, test and vote by Thursday, February 15th, 9AM PST
> >> ***
> >>>
> >>> 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/~stanislavkozlovski/kafka-3.7.0-rc4/
> >>>
> >>> * Docker release artifact to be voted upon:
> >>> apache/kafka:3.7.0-rc4
> >>>
> >>> * Maven artifacts to be voted upon:
> >>>

Re: [VOTE] 3.7.0 RC4

2024-02-16 Thread Vedarth Sharma

Hey Stanislav,

Thanks for the release candidate.

+1 (non-binding)

I tested and verified the docker image artifact apache/kafka:3.7.0-rc4:-
- verified create topic, produce messages and consume messages flow when
running the docker image with
- default configs
- configs provided via env variables
- configs provided via file input
- verified the html documentation for docker image.
- ran the example docker compose files successfully.

All looks good for the docker image artifact!

Thanks and regards,
Vedarth


On Thu, Feb 15, 2024 at 10:58 PM Mickael Maison 
wrote:

> Hi Stanislav,
>
> Thanks for running the release.
>
> I did the following testing:
> - verified the check sums and signatures
> - ran ZooKeeper and KRaft quickstarts with Scala 2.13 binaries
> - ran a successful migration from ZooKeeper to KRaft
>
> We seem to be missing the upgrade notes for 3.7.0 in the docs. See
> https://kafka.apache.org/37/documentation.html#upgrade that still
> points to 3.6.0
> Before voting I'd like to see results from the system tests too.
>
> Thanks,
> Mickael
>
> On Thu, Feb 15, 2024 at 6:06 PM Andrew Schofield
>  wrote:
> >
> > +1 (non-binding). I used the staged binaries with Scala 2.13. I tried
> the new group coordinator
> > and consumer group protocol which is included with the Early Access
> release of KIP-848.
> > Also verified the availability of the new APIs. All working as expected.
> >
> > Thanks,
> > Andrew
> >
> > > On 15 Feb 2024, at 05:07, Paolo Patierno 
> wrote:
> > >
> > > +1 (non-binding). I used the staged binaries with Scala 2.13 and mostly
> > > focused on the ZooKeeper to KRaft migration with multiple tests.
> Everything
> > > works fine.
> > >
> > > Thanks
> > > Paolo
> > >
> > > On Mon, 12 Feb 2024, 22:06 Jakub Scholz,  wrote:
> > >
> > >> +1 (non-binding). I used the staged binaries with Scala 2.13 and the
> staged
> > >> Maven artifacts to run my tests. All seems to work fine. Thanks.
> > >>
> > >> Jakub
> > >>
> > >> On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
> > >>  wrote:
> > >>
> > >>> Hello Kafka users, developers and client-developers,
> > >>>
> > >>> This is the second candidate we are considering for release of Apache
> > >> Kafka
> > >>> 3.7.0.
> > >>>
> > >>> Major changes include:
> > >>> - Early Access to KIP-848 - the next generation of the consumer
> rebalance
> > >>> protocol
> > >>> - Early Access to KIP-858: Adding JBOD support to KRaft
> > >>> - KIP-714: Observability into Client metrics via a standardized
> interface
> > >>>
> > >>> Release notes for the 3.7.0 release:
> > >>>
> > >>>
> > >>
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
> > >>>
> > >>> *** Please download, test and vote by Thursday, February 15th, 9AM
> PST
> > >> ***
> > >>>
> > >>> 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/~stanislavkozlovski/kafka-3.7.0-rc4/
> > >>>
> > >>> * Docker release artifact to be voted upon:
> > >>> apache/kafka:3.7.0-rc4
> > >>>
> > >>> * Maven artifacts to be voted upon:
> > >>>
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > >>>
> > >>> * Javadoc:
> > >>> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/javadoc/
> > >>>
> > >>> * Tag to be voted upon (off 3.7 branch) is the 3.7.0 tag:
> > >>> https://github.com/apache/kafka/releases/tag/3.7.0-rc4
> > >>>
> > >>> * Documentation:
> > >>> https://kafka.apache.org/37/documentation.html
> > >>>
> > >>> * Protocol:
> > >>> https://kafka.apache.org/37/protocol.html
> > >>>
> > >>> * Successful Jenkins builds for the 3.7 branch:
> > >>>
> > >>> Unit/integration tests: I am in the process of running and analyzing
> > >> these.
> > >>> System tests: I am in the process of running these.
> > >>>
> > >>> Expect a follow-up over the weekend
> > >>>
> > >>> * Successful Docker Image Github Actions Pipeline for 3.7 branch:
> > >>> Docker Build Test Pipeline:
> > >>> https://github.com/apache/kafka/actions/runs/7845614846
> > >>>
> > >>> /**
> > >>>
> > >>> Best,
> > >>> Stanislav
> > >>>
> > >>
> >
>

Re: [VOTE] 3.7.0 RC4

2024-02-15 Thread Mickael Maison

Hi Stanislav,

Thanks for running the release.

I did the following testing:
- verified the check sums and signatures
- ran ZooKeeper and KRaft quickstarts with Scala 2.13 binaries
- ran a successful migration from ZooKeeper to KRaft

We seem to be missing the upgrade notes for 3.7.0 in the docs. See
https://kafka.apache.org/37/documentation.html#upgrade that still
points to 3.6.0
Before voting I'd like to see results from the system tests too.

Thanks,
Mickael

On Thu, Feb 15, 2024 at 6:06 PM Andrew Schofield
 wrote:
>
> +1 (non-binding). I used the staged binaries with Scala 2.13. I tried the new 
> group coordinator
> and consumer group protocol which is included with the Early Access release 
> of KIP-848.
> Also verified the availability of the new APIs. All working as expected.
>
> Thanks,
> Andrew
>
> > On 15 Feb 2024, at 05:07, Paolo Patierno  wrote:
> >
> > +1 (non-binding). I used the staged binaries with Scala 2.13 and mostly
> > focused on the ZooKeeper to KRaft migration with multiple tests. Everything
> > works fine.
> >
> > Thanks
> > Paolo
> >
> > On Mon, 12 Feb 2024, 22:06 Jakub Scholz,  wrote:
> >
> >> +1 (non-binding). I used the staged binaries with Scala 2.13 and the staged
> >> Maven artifacts to run my tests. All seems to work fine. Thanks.
> >>
> >> Jakub
> >>
> >> On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
> >>  wrote:
> >>
> >>> Hello Kafka users, developers and client-developers,
> >>>
> >>> This is the second candidate we are considering for release of Apache
> >> Kafka
> >>> 3.7.0.
> >>>
> >>> Major changes include:
> >>> - Early Access to KIP-848 - the next generation of the consumer rebalance
> >>> protocol
> >>> - Early Access to KIP-858: Adding JBOD support to KRaft
> >>> - KIP-714: Observability into Client metrics via a standardized interface
> >>>
> >>> Release notes for the 3.7.0 release:
> >>>
> >>>
> >> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
> >>>
> >>> *** Please download, test and vote by Thursday, February 15th, 9AM PST
> >> ***
> >>>
> >>> 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/~stanislavkozlovski/kafka-3.7.0-rc4/
> >>>
> >>> * Docker release artifact to be voted upon:
> >>> apache/kafka:3.7.0-rc4
> >>>
> >>> * Maven artifacts to be voted upon:
> >>> https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >>>
> >>> * Javadoc:
> >>> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/javadoc/
> >>>
> >>> * Tag to be voted upon (off 3.7 branch) is the 3.7.0 tag:
> >>> https://github.com/apache/kafka/releases/tag/3.7.0-rc4
> >>>
> >>> * Documentation:
> >>> https://kafka.apache.org/37/documentation.html
> >>>
> >>> * Protocol:
> >>> https://kafka.apache.org/37/protocol.html
> >>>
> >>> * Successful Jenkins builds for the 3.7 branch:
> >>>
> >>> Unit/integration tests: I am in the process of running and analyzing
> >> these.
> >>> System tests: I am in the process of running these.
> >>>
> >>> Expect a follow-up over the weekend
> >>>
> >>> * Successful Docker Image Github Actions Pipeline for 3.7 branch:
> >>> Docker Build Test Pipeline:
> >>> https://github.com/apache/kafka/actions/runs/7845614846
> >>>
> >>> /**
> >>>
> >>> Best,
> >>> Stanislav
> >>>
> >>
>

Re: [VOTE] 3.7.0 RC4

2024-02-15 Thread Andrew Schofield

+1 (non-binding). I used the staged binaries with Scala 2.13. I tried the new 
group coordinator
and consumer group protocol which is included with the Early Access release of 
KIP-848.
Also verified the availability of the new APIs. All working as expected.

Thanks,
Andrew

> On 15 Feb 2024, at 05:07, Paolo Patierno  wrote:
>
> +1 (non-binding). I used the staged binaries with Scala 2.13 and mostly
> focused on the ZooKeeper to KRaft migration with multiple tests. Everything
> works fine.
>
> Thanks
> Paolo
>
> On Mon, 12 Feb 2024, 22:06 Jakub Scholz,  wrote:
>
>> +1 (non-binding). I used the staged binaries with Scala 2.13 and the staged
>> Maven artifacts to run my tests. All seems to work fine. Thanks.
>>
>> Jakub
>>
>> On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
>>  wrote:
>>
>>> Hello Kafka users, developers and client-developers,
>>>
>>> This is the second candidate we are considering for release of Apache
>> Kafka
>>> 3.7.0.
>>>
>>> Major changes include:
>>> - Early Access to KIP-848 - the next generation of the consumer rebalance
>>> protocol
>>> - Early Access to KIP-858: Adding JBOD support to KRaft
>>> - KIP-714: Observability into Client metrics via a standardized interface
>>>
>>> Release notes for the 3.7.0 release:
>>>
>>>
>> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
>>>
>>> *** Please download, test and vote by Thursday, February 15th, 9AM PST
>> ***
>>>
>>> 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/~stanislavkozlovski/kafka-3.7.0-rc4/
>>>
>>> * Docker release artifact to be voted upon:
>>> apache/kafka:3.7.0-rc4
>>>
>>> * Maven artifacts to be voted upon:
>>> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>>>
>>> * Javadoc:
>>> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/javadoc/
>>>
>>> * Tag to be voted upon (off 3.7 branch) is the 3.7.0 tag:
>>> https://github.com/apache/kafka/releases/tag/3.7.0-rc4
>>>
>>> * Documentation:
>>> https://kafka.apache.org/37/documentation.html
>>>
>>> * Protocol:
>>> https://kafka.apache.org/37/protocol.html
>>>
>>> * Successful Jenkins builds for the 3.7 branch:
>>>
>>> Unit/integration tests: I am in the process of running and analyzing
>> these.
>>> System tests: I am in the process of running these.
>>>
>>> Expect a follow-up over the weekend
>>>
>>> * Successful Docker Image Github Actions Pipeline for 3.7 branch:
>>> Docker Build Test Pipeline:
>>> https://github.com/apache/kafka/actions/runs/7845614846
>>>
>>> /**
>>>
>>> Best,
>>> Stanislav
>>>
>>

Re: [VOTE] 3.7.0 RC4

2024-02-14 Thread Paolo Patierno

+1 (non-binding). I used the staged binaries with Scala 2.13 and mostly
focused on the ZooKeeper to KRaft migration with multiple tests. Everything
works fine.

Thanks
Paolo

On Mon, 12 Feb 2024, 22:06 Jakub Scholz,  wrote:

> +1 (non-binding). I used the staged binaries with Scala 2.13 and the staged
> Maven artifacts to run my tests. All seems to work fine. Thanks.
>
> Jakub
>
> On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
>  wrote:
>
> > Hello Kafka users, developers and client-developers,
> >
> > This is the second candidate we are considering for release of Apache
> Kafka
> > 3.7.0.
> >
> > Major changes include:
> > - Early Access to KIP-848 - the next generation of the consumer rebalance
> > protocol
> > - Early Access to KIP-858: Adding JBOD support to KRaft
> > - KIP-714: Observability into Client metrics via a standardized interface
> >
> > Release notes for the 3.7.0 release:
> >
> >
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
> >
> > *** Please download, test and vote by Thursday, February 15th, 9AM PST
> ***
> >
> > 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/~stanislavkozlovski/kafka-3.7.0-rc4/
> >
> > * Docker release artifact to be voted upon:
> > apache/kafka:3.7.0-rc4
> >
> > * Maven artifacts to be voted upon:
> > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >
> > * Javadoc:
> > https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/javadoc/
> >
> > * Tag to be voted upon (off 3.7 branch) is the 3.7.0 tag:
> > https://github.com/apache/kafka/releases/tag/3.7.0-rc4
> >
> > * Documentation:
> > https://kafka.apache.org/37/documentation.html
> >
> > * Protocol:
> > https://kafka.apache.org/37/protocol.html
> >
> > * Successful Jenkins builds for the 3.7 branch:
> >
> > Unit/integration tests: I am in the process of running and analyzing
> these.
> > System tests: I am in the process of running these.
> >
> > Expect a follow-up over the weekend
> >
> > * Successful Docker Image Github Actions Pipeline for 3.7 branch:
> > Docker Build Test Pipeline:
> > https://github.com/apache/kafka/actions/runs/7845614846
> >
> > /**
> >
> > Best,
> > Stanislav
> >
>

Re: [VOTE] 3.7.0 RC4

2024-02-14 Thread Justine Olshan

I just merged a PR to trunk that fixes some of the LogDirFailureTests.

I believe the issue is mostly related to the tests and not the code. Not
sure if we think it is necessary to hotfix since the change was in the
tests.
https://github.com/apache/kafka/commit/be6653c8bc25717e25a7db164527635a6579b4cc

Thanks for the results and the gist!

Justine

On Wed, Feb 14, 2024 at 11:53 AM Stanislav Kozlovski
 wrote:

> Hey Justine,
>
> Good question. I have been running the system tests and I have been
> preparing a doc to share. I got one run completed and was waiting for a
> second one to cross-check, but unfortunately I had a build take 35+ hours
> and canceled it. I'm currently 6h into the second one, expecting it to
> complete in 11h or so.
>
> There were quite a bit, so I was looking forward to get another run in to
> cross-check the flakes:
> -
>
> https://gist.githubusercontent.com/stanislavkozlovski/3a97fc7602f3fee40cb374f1343d46b6/raw/b9de6e0eb975e8234d43bc725982096e47fd0457/rc4_test_failures_system_test_run_1.md
>
> I also checked the integration tests and saw
> - kafka.server.LogDirFailureTest.testProduceErrorFromFailureOnLogRoll
> - kafka.server.LogDirFailureTest.testIOExceptionDuringLogRoll
> failed three timed in a row.
>
> Here is the gist with the results:
> https://gist.github.com/stanislavkozlovski/820976fc7bfb5f4dcdf9742fd96a9982
>
>
>
> On Wed, Feb 14, 2024 at 6:31 PM Justine Olshan
> 
> wrote:
>
> > Hey Stan,
> > Did we ever get system tests results? I can also start a run
> >
> > On Mon, Feb 12, 2024 at 1:06 PM Jakub Scholz  wrote:
> >
> > > +1 (non-binding). I used the staged binaries with Scala 2.13 and the
> > staged
> > > Maven artifacts to run my tests. All seems to work fine. Thanks.
> > >
> > > Jakub
> > >
> > > On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
> > >  wrote:
> > >
> > > > Hello Kafka users, developers and client-developers,
> > > >
> > > > This is the second candidate we are considering for release of Apache
> > > Kafka
> > > > 3.7.0.
> > > >
> > > > Major changes include:
> > > > - Early Access to KIP-848 - the next generation of the consumer
> > rebalance
> > > > protocol
> > > > - Early Access to KIP-858: Adding JBOD support to KRaft
> > > > - KIP-714: Observability into Client metrics via a standardized
> > interface
> > > >
> > > > Release notes for the 3.7.0 release:
> > > >
> > > >
> > >
> >
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
> > > >
> > > > *** Please download, test and vote by Thursday, February 15th, 9AM
> PST
> > > ***
> > > >
> > > > 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/~stanislavkozlovski/kafka-3.7.0-rc4/
> > > >
> > > > * Docker release artifact to be voted upon:
> > > > apache/kafka:3.7.0-rc4
> > > >
> > > > * Maven artifacts to be voted upon:
> > > >
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > > >
> > > > * Javadoc:
> > > > https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/javadoc/
> > > >
> > > > * Tag to be voted upon (off 3.7 branch) is the 3.7.0 tag:
> > > > https://github.com/apache/kafka/releases/tag/3.7.0-rc4
> > > >
> > > > * Documentation:
> > > > https://kafka.apache.org/37/documentation.html
> > > >
> > > > * Protocol:
> > > > https://kafka.apache.org/37/protocol.html
> > > >
> > > > * Successful Jenkins builds for the 3.7 branch:
> > > >
> > > > Unit/integration tests: I am in the process of running and analyzing
> > > these.
> > > > System tests: I am in the process of running these.
> > > >
> > > > Expect a follow-up over the weekend
> > > >
> > > > * Successful Docker Image Github Actions Pipeline for 3.7 branch:
> > > > Docker Build Test Pipeline:
> > > > https://github.com/apache/kafka/actions/runs/7845614846
> > > >
> > > > /**
> > > >
> > > > Best,
> > > > Stanislav
> > > >
> > >
> >
>
>
> --
> Best,
> Stanislav
>

Re: [VOTE] 3.7.0 RC4

2024-02-14 Thread Stanislav Kozlovski

Hey Justine,

Good question. I have been running the system tests and I have been
preparing a doc to share. I got one run completed and was waiting for a
second one to cross-check, but unfortunately I had a build take 35+ hours
and canceled it. I'm currently 6h into the second one, expecting it to
complete in 11h or so.

There were quite a bit, so I was looking forward to get another run in to
cross-check the flakes:
-
https://gist.githubusercontent.com/stanislavkozlovski/3a97fc7602f3fee40cb374f1343d46b6/raw/b9de6e0eb975e8234d43bc725982096e47fd0457/rc4_test_failures_system_test_run_1.md

I also checked the integration tests and saw
- kafka.server.LogDirFailureTest.testProduceErrorFromFailureOnLogRoll
- kafka.server.LogDirFailureTest.testIOExceptionDuringLogRoll
failed three timed in a row.

Here is the gist with the results:
https://gist.github.com/stanislavkozlovski/820976fc7bfb5f4dcdf9742fd96a9982



On Wed, Feb 14, 2024 at 6:31 PM Justine Olshan 
wrote:

> Hey Stan,
> Did we ever get system tests results? I can also start a run
>
> On Mon, Feb 12, 2024 at 1:06 PM Jakub Scholz  wrote:
>
> > +1 (non-binding). I used the staged binaries with Scala 2.13 and the
> staged
> > Maven artifacts to run my tests. All seems to work fine. Thanks.
> >
> > Jakub
> >
> > On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
> >  wrote:
> >
> > > Hello Kafka users, developers and client-developers,
> > >
> > > This is the second candidate we are considering for release of Apache
> > Kafka
> > > 3.7.0.
> > >
> > > Major changes include:
> > > - Early Access to KIP-848 - the next generation of the consumer
> rebalance
> > > protocol
> > > - Early Access to KIP-858: Adding JBOD support to KRaft
> > > - KIP-714: Observability into Client metrics via a standardized
> interface
> > >
> > > Release notes for the 3.7.0 release:
> > >
> > >
> >
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
> > >
> > > *** Please download, test and vote by Thursday, February 15th, 9AM PST
> > ***
> > >
> > > 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/~stanislavkozlovski/kafka-3.7.0-rc4/
> > >
> > > * Docker release artifact to be voted upon:
> > > apache/kafka:3.7.0-rc4
> > >
> > > * Maven artifacts to be voted upon:
> > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > >
> > > * Javadoc:
> > > https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/javadoc/
> > >
> > > * Tag to be voted upon (off 3.7 branch) is the 3.7.0 tag:
> > > https://github.com/apache/kafka/releases/tag/3.7.0-rc4
> > >
> > > * Documentation:
> > > https://kafka.apache.org/37/documentation.html
> > >
> > > * Protocol:
> > > https://kafka.apache.org/37/protocol.html
> > >
> > > * Successful Jenkins builds for the 3.7 branch:
> > >
> > > Unit/integration tests: I am in the process of running and analyzing
> > these.
> > > System tests: I am in the process of running these.
> > >
> > > Expect a follow-up over the weekend
> > >
> > > * Successful Docker Image Github Actions Pipeline for 3.7 branch:
> > > Docker Build Test Pipeline:
> > > https://github.com/apache/kafka/actions/runs/7845614846
> > >
> > > /**
> > >
> > > Best,
> > > Stanislav
> > >
> >
>


-- 
Best,
Stanislav

Re: [VOTE] 3.7.0 RC4

2024-02-14 Thread Justine Olshan

Hey Stan,
Did we ever get system tests results? I can also start a run

On Mon, Feb 12, 2024 at 1:06 PM Jakub Scholz  wrote:

> +1 (non-binding). I used the staged binaries with Scala 2.13 and the staged
> Maven artifacts to run my tests. All seems to work fine. Thanks.
>
> Jakub
>
> On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
>  wrote:
>
> > Hello Kafka users, developers and client-developers,
> >
> > This is the second candidate we are considering for release of Apache
> Kafka
> > 3.7.0.
> >
> > Major changes include:
> > - Early Access to KIP-848 - the next generation of the consumer rebalance
> > protocol
> > - Early Access to KIP-858: Adding JBOD support to KRaft
> > - KIP-714: Observability into Client metrics via a standardized interface
> >
> > Release notes for the 3.7.0 release:
> >
> >
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
> >
> > *** Please download, test and vote by Thursday, February 15th, 9AM PST
> ***
> >
> > 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/~stanislavkozlovski/kafka-3.7.0-rc4/
> >
> > * Docker release artifact to be voted upon:
> > apache/kafka:3.7.0-rc4
> >
> > * Maven artifacts to be voted upon:
> > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >
> > * Javadoc:
> > https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/javadoc/
> >
> > * Tag to be voted upon (off 3.7 branch) is the 3.7.0 tag:
> > https://github.com/apache/kafka/releases/tag/3.7.0-rc4
> >
> > * Documentation:
> > https://kafka.apache.org/37/documentation.html
> >
> > * Protocol:
> > https://kafka.apache.org/37/protocol.html
> >
> > * Successful Jenkins builds for the 3.7 branch:
> >
> > Unit/integration tests: I am in the process of running and analyzing
> these.
> > System tests: I am in the process of running these.
> >
> > Expect a follow-up over the weekend
> >
> > * Successful Docker Image Github Actions Pipeline for 3.7 branch:
> > Docker Build Test Pipeline:
> > https://github.com/apache/kafka/actions/runs/7845614846
> >
> > /**
> >
> > Best,
> > Stanislav
> >
>

Re: [VOTE] 3.7.0 RC4

2024-02-12 Thread Jakub Scholz

+1 (non-binding). I used the staged binaries with Scala 2.13 and the staged
Maven artifacts to run my tests. All seems to work fine. Thanks.

Jakub

On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
 wrote:

> Hello Kafka users, developers and client-developers,
>
> This is the second candidate we are considering for release of Apache Kafka
> 3.7.0.
>
> Major changes include:
> - Early Access to KIP-848 - the next generation of the consumer rebalance
> protocol
> - Early Access to KIP-858: Adding JBOD support to KRaft
> - KIP-714: Observability into Client metrics via a standardized interface
>
> Release notes for the 3.7.0 release:
>
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
>
> *** Please download, test and vote by Thursday, February 15th, 9AM PST ***
>
> 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/~stanislavkozlovski/kafka-3.7.0-rc4/
>
> * Docker release artifact to be voted upon:
> apache/kafka:3.7.0-rc4
>
> * Maven artifacts to be voted upon:
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>
> * Javadoc:
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/javadoc/
>
> * Tag to be voted upon (off 3.7 branch) is the 3.7.0 tag:
> https://github.com/apache/kafka/releases/tag/3.7.0-rc4
>
> * Documentation:
> https://kafka.apache.org/37/documentation.html
>
> * Protocol:
> https://kafka.apache.org/37/protocol.html
>
> * Successful Jenkins builds for the 3.7 branch:
>
> Unit/integration tests: I am in the process of running and analyzing these.
> System tests: I am in the process of running these.
>
> Expect a follow-up over the weekend
>
> * Successful Docker Image Github Actions Pipeline for 3.7 branch:
> Docker Build Test Pipeline:
> https://github.com/apache/kafka/actions/runs/7845614846
>
> /**
>
> Best,
> Stanislav
>

Re: [VOTE] 3.7.0 RC4

2024-02-12 Thread Josep Prat

Hi Stanislav,

Thanks for running the release. It gets a +1 (non-binding) from me.
I run the following steps to validate:
- Compiled with Java 17 and Scala 2.13.12
- Run unit and integration tests
  - "LogDirFailureTest > testIOExceptionDuringLogRoll(String).quorum=kraft"
failed[1] several times before I could get a clear build.
- Checked JavaDoc and clicked links pointing to JDK
- Run getting started with ZK and KRaft
- Verified artifact's signatures and hashes

Best,

[1]: Gradle Test Run :core:test > Gradle Test Executor 159 >
LogDirFailureTest > testIOExceptionDuringLogRoll(String) >
testIOExceptionDuringLogRoll(String).quorum=kraft FAILED
org.opentest4j.AssertionFailedError: expected:  but was: 
at
app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at
app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
at
app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
at
app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31)
at
app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:179)
at
app//kafka.utils.TestUtils$.causeLogDirFailure(TestUtils.scala:1671)
at
app//kafka.server.LogDirFailureTest.testProduceAfterLogDirFailureOnLeader(LogDirFailureTest.scala:186)
at
app//kafka.server.LogDirFailureTest.testIOExceptionDuringLogRoll(LogDirFailureTest.scala:70)

On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski
 wrote:

> Hello Kafka users, developers and client-developers,
>
> This is the second candidate we are considering for release of Apache Kafka
> 3.7.0.
>
> Major changes include:
> - Early Access to KIP-848 - the next generation of the consumer rebalance
> protocol
> - Early Access to KIP-858: Adding JBOD support to KRaft
> - KIP-714: Observability into Client metrics via a standardized interface
>
> Release notes for the 3.7.0 release:
>
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/RELEASE_NOTES.html
>
> *** Please download, test and vote by Thursday, February 15th, 9AM PST ***
>
> 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/~stanislavkozlovski/kafka-3.7.0-rc4/
>
> * Docker release artifact to be voted upon:
> apache/kafka:3.7.0-rc4
>
> * Maven artifacts to be voted upon:
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>
> * Javadoc:
> https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc4/javadoc/
>
> * Tag to be voted upon (off 3.7 branch) is the 3.7.0 tag:
> https://github.com/apache/kafka/releases/tag/3.7.0-rc4
>
> * Documentation:
> https://kafka.apache.org/37/documentation.html
>
> * Protocol:
> https://kafka.apache.org/37/protocol.html
>
> * Successful Jenkins builds for the 3.7 branch:
>
> Unit/integration tests: I am in the process of running and analyzing these.
> System tests: I am in the process of running these.
>
> Expect a follow-up over the weekend
>
> * Successful Docker Image Github Actions Pipeline for 3.7 branch:
> Docker Build Test Pipeline:
> https://github.com/apache/kafka/actions/runs/7845614846
>
> /**
>
> Best,
> Stanislav
>


-- 
[image: Aiven] 

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io    |   
     
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

Re: [VOTE] 3.7.0 RC4

31 matches

Site Navigation

Mail list logo

Footer information