Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.6 #65

[Apache Jenkins Server]

See 

Re: [ANNOUNCE] New Kafka PMC Member: Justine Olshan

[ziming deng]

Congratulations Justine!


> On Sep 25, 2023, at 00:01, Viktor Somogyi-Vass 
>  wrote:
> 
> Congrats Justine!
> 
> On Sun, Sep 24, 2023, 17:45 Kirk True  wrote:
> 
>> Congratulations Justine! Thanks for all your great work!
>> 
>>> On Sep 24, 2023, at 8:37 AM, John Roesler  wrote:
>>> 
>>> Congratulations, Justine!
>>> -John
>>> 
>>> On Sun, Sep 24, 2023, at 05:05, Mickael Maison wrote:
 Congratulations Justine!
 
 On Sun, Sep 24, 2023 at 5:04 AM Sophie Blee-Goldman
  wrote:
> 
> Congrats Justine!
> 
> On Sat, Sep 23, 2023, 4:36 PM Tom Bentley  wrote:
> 
>> Congratulations!
>> 
>> On Sun, 24 Sept 2023 at 12:32, Satish Duggana <
>> satish.dugg...@gmail.com>
>> wrote:
>> 
>>> Congratulations Justine!!
>>> 
>>> On Sat, 23 Sept 2023 at 15:46, Bill Bejeck 
>> wrote:
 
 Congrats Justine!
 
 -Bill
 
 On Sat, Sep 23, 2023 at 6:23 PM Greg Harris
>> >>> 
 wrote:
 
> Congratulations Justine!
> 
> On Sat, Sep 23, 2023 at 5:49 AM Boudjelda Mohamed Said
>  wrote:
>> 
>> Congrats Justin !
>> 
>> On Sat 23 Sep 2023 at 14:44, Randall Hauch 
>> wrote:
>> 
>>> Congratulations, Justine!
>>> 
>>> On Sat, Sep 23, 2023 at 4:25 AM Kamal Chandraprakash <
>>> kamal.chandraprak...@gmail.com> wrote:
>>> 
 Congrats Justine!
 
 On Sat, Sep 23, 2023, 13:28 Divij Vaidya <
>>> divijvaidy...@gmail.com>
>>> wrote:
 
> Congratulations Justine!
> 
> On Sat 23. Sep 2023 at 07:06, Chris Egerton <
> fearthecel...@gmail.com>
> wrote:
> 
>> Congrats Justine!
>> On Fri, Sep 22, 2023, 20:47 Guozhang Wang <
>>> guozhang.wang...@gmail.com>
>> wrote:
>> 
>>> Congratulations!
>>> 
>>> On Fri, Sep 22, 2023 at 8:44 PM Tzu-Li (Gordon) Tai <
> tzuli...@apache.org
>>> 
>>> wrote:
 
 Congratulations Justine!
 
 On Fri, Sep 22, 2023, 19:25 Philip Nee <
>>> philip...@gmail.com>
 wrote:
 
> Congrats Justine!
> 
> On Fri, Sep 22, 2023 at 7:07 PM Luke Chen <
> show...@gmail.com>
> wrote:
> 
>> Hi, Everyone,
>> 
>> Justine Olshan has been a Kafka committer since
>> Dec.
> 2022.
>>> She
> has
>>> been
>> very active and instrumental to the community since
> becoming
>>> a
>>> committer.
>> It's my pleasure to announce that Justine is now a
> member of
> Kafka
>>> PMC.
>> 
>> Congratulations Justine!
>> 
>> Luke
>> on behalf of Apache Kafka PMC
>> 
> 
>>> 
>> 
> 
 
>>> 
> 
>>> 
>>> 
>> 
>> 
>> 

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.6 #64

[Apache Jenkins Server]

See 

[jira] [Created] (KAFKA-15497) Refactor build.gradle and split each module configuration on the module itself

[Said BOUDJELDA (Jira)]

Said BOUDJELDA created KAFKA-15497:
--

 Summary: Refactor build.gradle and split each module configuration 
on the module itself 
 Key: KAFKA-15497
 URL: https://issues.apache.org/jira/browse/KAFKA-15497
 Project: Kafka
  Issue Type: Improvement
Reporter: Said BOUDJELDA


The *build.gradle* file is getting too big and hard to maintain, a good reason 
to split this files over modules of the project, and let the root 
*build.gradle* file manage just the common parts of the projet, this will 
increase readability

 

 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-15496) Upgrade Jetty to version 11.0.16

[Said BOUDJELDA (Jira)]

Said BOUDJELDA created KAFKA-15496:
--

 Summary: Upgrade Jetty to version 11.0.16
 Key: KAFKA-15496
 URL: https://issues.apache.org/jira/browse/KAFKA-15496
 Project: Kafka
  Issue Type: Improvement
Reporter: Said BOUDJELDA


Check release notes 
[https://github.com/eclipse/jetty.project/releases/tag/jetty-11.0.16] 

This task cannot be achieved without the upgrade of *jackson-databind*  library 
 please check for more details KAFKA-15208 for more details 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[Justine Olshan]

Hi Satish,

I've done the following:
- Verified signature
- Built from Java 17/Scala 2.13 and Java 8/Scala 2.11
- Run unit + integration tests
- Ran a shorter Trogdor transactional-produce-bench on a single broker
cluster (KRaft and ZK) to verify transactional workloads worked reasonably

Minor thing (we can discuss elsewhere and is non-blocking for the release)
but if ZK has been deprecated since 3.5 we should move up the Kraft setup
in the quickstart guide  here
.

+1 (binding) from me.

Justine

On Sun, Sep 24, 2023 at 7:09 AM Federico Valeri 
wrote:

> Hi Satish, I did the following to verify the release:
>
> - Verified signature and checksum
> - Built from source with Java 17 and Scala 2.13
> - Ran all unit and integration tests
> - Spot checked release notes and documentation
> - Ran a custom client using staging artifacts on a 3-nodes cluster
> - Tested tiered storage with one of the available RSM implementations
>
> +1 (non binding)
>
> Thanks
> Fede
>
>
> On Sun, Sep 24, 2023 at 8:49 AM Luke Chen  wrote:
> >
> > Hi Satish,
> >
> > I verified with:
> > 1. Ran quick start in KRaft for scala 2.12 artifact
> > 2. Making sure the checksum are correct
> > 3. Browsing release notes, documents, javadocs, protocols.
> >
> > I filed KAFKA-15491  >for
> > log output improvement while testing stream application.
> > It won't be blocker in v3.6.0.
> >
> > For KAFKA-15489 , I'm
> > fine if we decide to fix it in v3.6.1/v3.7.0.
> >
> > +1 (binding) from me.
> >
> > Thank you.
> > Luke
> >
> > On Sun, Sep 24, 2023 at 3:38 AM Ismael Juma  wrote:
> >
> > > Given that this is not a regression and there have been no reports for
> over
> > > a year, I think it's ok for this to land in 3.6.1.
> > >
> > > Ismael
> > >
> > > On Sat, Sep 23, 2023 at 9:32 AM Satish Duggana <
> satish.dugg...@gmail.com>
> > > wrote:
> > >
> > > > Thanks Luke for reporting KRaft issue[1].
> > > >
> > > > I am not sure whether it is a release blocker for 3.6.0. Need input
> > > > from other KRaft experts also to finalize the decision. Even if we
> > > > adopt a fix, do not we need to bake it for some time before it is
> > > > pushed to production to avoid any regressions as this change is in
> the
> > > > critical paths?
> > > >
> > > > 1. https://issues.apache.org/jira/browse/KAFKA-15489
> > > >
> > > > Thanks,
> > > > Satish.
> > > >
> > > > On Sat, 23 Sept 2023 at 03:08, Luke Chen  wrote:
> > > > >
> > > > > Hi Satish,
> > > > >
> > > > > I found the current KRaft implementation will have "split brain"
> issue
> > > > when
> > > > > network partition happens, which will cause inconsistent metadata
> > > > returned
> > > > > from the controller.
> > > > > Filed KAFKA-15489 <
> https://issues.apache.org/jira/browse/KAFKA-15489>
> > > > for
> > > > > this issue, and PR  is
> > > ready
> > > > > for review.
> > > > >
> > > > > Even though this is not a regression issue (this has already
> existed
> > > > since
> > > > > the 1st release of KRaft feature), I think this is an important
> issue
> > > > since
> > > > > KRaft is announced production ready.
> > > > > Not sure what other people's thoughts are.
> > > > >
> > > > > Thank you.
> > > > > Luke
> > > > >
> > > > > On Thu, Sep 21, 2023 at 6:33 PM Josep Prat
>  > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Satish,
> > > > > >
> > > > > > I ran the following validation steps:
> > > > > > - Built from source with Java 11 and Scala 2.13
> > > > > > - Verified Signatures and hashes of the artifacts generated
> > > > > > - Navigated through Javadoc including links to JDK classes
> > > > > > - Run the unit tests
> > > > > > - Run integration tests
> > > > > > - Run the quickstart in KRaft and Zookeeper mode
> > > > > >
> > > > > >
> > > > > > I +1 this release (non-binding)
> > > > > >
> > > > > > Thanks for your efforts!
> > > > > >
> > > > > > On Thu, Sep 21, 2023 at 2:59 AM Satish Duggana <
> > > > satish.dugg...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks Greg for verifying the release including the earlier
> > > > > > > blocker(KAFKA-15473) verification.
> > > > > > >
> > > > > > > ~Satish.
> > > > > > >
> > > > > > > On Wed, 20 Sept 2023 at 22:30, Greg Harris
> > > >  > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > I verified the functionality of KIP-898 and the recent fix
> for
> > > > > > > > KAFKA-15473 with the following steps:
> > > > > > > >
> > > > > > > > 1. I started a 3.5.1 broker, and a 3.5.1 worker with most
> (>400)
> > > > > > > > publicly available plugins installed
> > > > > > > > 2. I captured the output of /connector-plugins
> > > > > > > > 3. I upgraded the worker to 3.6.0-rc1
> > > > > > > > 4. I captured the output of /connector-plugins with various
> > > > settings
> > > > > > > > of 

Re: [VOTE] KIP-858: Handle JBOD broker disk failure in KRaft

[Ron Dagostino]

Hi Igor.  I've opened
https://issues.apache.org/jira/browse/KAFKA-15495 to identify the data
loss scenario that I was referring to, including steps on how to
reproduce it.  I agree this is a separate issue from JBOD per se.  The
disk UUID that this KIP introduces does give us the ability to avoid
loss of data in the scenario described in that ticket.

Ron

On Sat, Sep 23, 2023 at 9:08 AM Igor Soarez  wrote:
>
> Hi everyone,
>
> I believe we can close this voting thread now, as there
> were three +1 binding votes from Ziming, Mickael and Ron.
> With that, this vote passes.
>
> Thanks to everyone who participated in reviewing,
> and/or taking the time to vote on this KIP!
>
> Best,
>
> --
> Igor

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

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 317186 lines...]

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
onlyRemovePendingTaskToSuspendShouldRemoveTaskFromPendingUpdateActions() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
onlyRemovePendingTaskToSuspendShouldRemoveTaskFromPendingUpdateActions() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldOnlyKeepLastUpdateAction() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldOnlyKeepLastUpdateAction() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldAddAndRemovePendingTaskToRecycle() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldAddAndRemovePendingTaskToRecycle() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
onlyRemovePendingTaskToUpdateInputPartitionsShouldRemoveTaskFromPendingUpdateActions()
 STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
onlyRemovePendingTaskToUpdateInputPartitionsShouldRemoveTaskFromPendingUpdateActions()
 PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldVerifyIfPendingTaskToRecycleExist() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldVerifyIfPendingTaskToRecycleExist() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldAddAndRemovePendingTaskToUpdateInputPartitions() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldAddAndRemovePendingTaskToUpdateInputPartitions() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
onlyRemovePendingTaskToCloseDirtyShouldRemoveTaskFromPendingUpdateActions() 
STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
onlyRemovePendingTaskToCloseDirtyShouldRemoveTaskFromPendingUpdateActions() 
PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldAddAndRemovePendingTaskToSuspend() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldAddAndRemovePendingTaskToSuspend() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldVerifyIfPendingTaskToInitExist() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldVerifyIfPendingTaskToInitExist() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
onlyRemovePendingTaskToCloseCleanShouldRemoveTaskFromPendingUpdateActions() 
STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
onlyRemovePendingTaskToCloseCleanShouldRemoveTaskFromPendingUpdateActions() 
PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldDrainPendingTasksToCreate() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldDrainPendingTasksToCreate() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
onlyRemovePendingTaskToRecycleShouldRemoveTaskFromPendingUpdateActions() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
onlyRemovePendingTaskToRecycleShouldRemoveTaskFromPendingUpdateActions() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldAddAndRemovePendingTaskToCloseClean() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldAddAndRemovePendingTaskToCloseClean() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldAddAndRemovePendingTaskToCloseDirty() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldAddAndRemovePendingTaskToCloseDirty() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldKeepAddedTasks() STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > TasksTest > 
shouldKeepAddedTasks() PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > StateQueryResultTest 
> More than one query result throws IllegalArgumentException STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > StateQueryResultTest 
> More than one query result throws IllegalArgumentException PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > StateQueryResultTest 
> Zero query results shouldn't error STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > StateQueryResultTest 
> Zero query results shouldn't error PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > StateQueryResultTest 
> Valid query results still works STARTED

Gradle Test Run :streams:test > Gradle Test Executor 85 > StateQueryResultTest 
> Valid query results still works PASSED

Gradle Test Run :streams:test > Gradle Test Executor 85 > 

[jira] [Created] (KAFKA-15495) KRaft partition truncated when the only ISR member restarts with and empty disk

[Ron Dagostino (Jira)]

Ron Dagostino created KAFKA-15495:
-

 Summary: KRaft partition truncated when the only ISR member 
restarts with and empty disk
 Key: KAFKA-15495
 URL: https://issues.apache.org/jira/browse/KAFKA-15495
 Project: Kafka
  Issue Type: Bug
Affects Versions: 3.5.1, 3.4.1, 3.3.2, 3.6.0
Reporter: Ron Dagostino


Assume a topic-partition in KRaft has just a single leader replica in the ISR.  
Assume next that this replica goes offline.  This replica's log will define the 
contents of that partition when the replica restarts, which is correct 
behavior.  However, assume now that the replica has a disk failure, and we then 
replace the failed disk with a new, empty disk that we also format with the 
storage tool so it has the correct cluster ID.  If we then restart the broker, 
the topic-partition will have no data in it, and any other replicas that might 
exist will truncate their logs to match.  See below for a step-by-step demo of 
how to reproduce this.

[KIP-858: Handle JBOD broker disk failure in 
KRaft|https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft]
 introduces the concept of a Disk UUID that we can use to solve this problem.  
Specifically, when the leader restarts with an empty (but correctly-formatted) 
disk, the actual UUID associated with the disk will be different.  The 
controller will notice upon broker re-registration that its disk UUID differs 
from what was previously registered.  Right now we have no way of detecting 
this situation, but the disk UUID gives us that capability.


STEPS TO REPRODUCE:

Create a single broker cluster with single controller.  The standard files 
under config/kraft work well:

bin/kafka-storage.sh random-uuid
J8qXRwI-Qyi2G0guFTiuYw

# ensure we start clean
/bin/rm -rf /tmp/kraft-broker-logs /tmp/kraft-controller-logs

bin/kafka-storage.sh format --cluster-id J8qXRwI-Qyi2G0guFTiuYw --config 
config/kraft/controller.properties
bin/kafka-storage.sh format --cluster-id J8qXRwI-Qyi2G0guFTiuYw --config 
config/kraft/broker.properties

bin/kafka-server-start.sh config/kraft/controller.properties
bin/kafka-server-start.sh config/kraft/broker.properties

bin/kafka-topics.sh --bootstrap-server localhost:9092 --create --topic foo1 
--partitions 1 --replication-factor 1

# create __consumer-offsets topics
bin/kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic foo1 
--from-beginning
^C

# confirm that __consumer_offsets topic partitions are all created and on 
broker with node id 2
bin/kafka-topics.sh --bootstrap-server localhost:9092 --describe

Now create 2 more brokers, with node IDs 3 and 4

cat config/kraft/broker.properties | sed 's/node.id=2/node.id=11/' | sed 
's/localhost:9092/localhost:9011/g' |  sed 
's#log.dirs=/tmp/kraft-broker-logs#log.dirs=/tmp/kraft-broker-logs11#' > 
config/kraft/broker11.properties
cat config/kraft/broker.properties | sed 's/node.id=2/node.id=12/' | sed 
's/localhost:9092/localhost:9012/g' |  sed 
's#log.dirs=/tmp/kraft-broker-logs#log.dirs=/tmp/kraft-broker-logs12#' > 
config/kraft/broker12.properties

# ensure we start clean
/bin/rm -rf /tmp/kraft-broker-logs11 /tmp/kraft-broker-logs12

bin/kafka-storage.sh format --cluster-id J8qXRwI-Qyi2G0guFTiuYw --config 
config/kraft/broker11.properties
bin/kafka-storage.sh format --cluster-id J8qXRwI-Qyi2G0guFTiuYw --config 
config/kraft/broker12.properties

bin/kafka-server-start.sh config/kraft/broker11.properties
bin/kafka-server-start.sh config/kraft/broker12.properties

# create a topic with a single partition replicated on two brokers
bin/kafka-topics.sh --bootstrap-server localhost:9092 --create --topic foo2 
--partitions 1 --replication-factor 2

# reassign partitions onto brokers with Node IDs 11 and 12
cat > /tmp/reassign.json <

Re: [ANNOUNCE] New Kafka PMC Member: Justine Olshan

[Viktor Somogyi-Vass]

Congrats Justine!

On Sun, Sep 24, 2023, 17:45 Kirk True  wrote:

> Congratulations Justine! Thanks for all your great work!
>
> > On Sep 24, 2023, at 8:37 AM, John Roesler  wrote:
> >
> > Congratulations, Justine!
> > -John
> >
> > On Sun, Sep 24, 2023, at 05:05, Mickael Maison wrote:
> >> Congratulations Justine!
> >>
> >> On Sun, Sep 24, 2023 at 5:04 AM Sophie Blee-Goldman
> >>  wrote:
> >>>
> >>> Congrats Justine!
> >>>
> >>> On Sat, Sep 23, 2023, 4:36 PM Tom Bentley  wrote:
> >>>
>  Congratulations!
> 
>  On Sun, 24 Sept 2023 at 12:32, Satish Duggana <
> satish.dugg...@gmail.com>
>  wrote:
> 
> > Congratulations Justine!!
> >
> > On Sat, 23 Sept 2023 at 15:46, Bill Bejeck 
> wrote:
> >>
> >> Congrats Justine!
> >>
> >> -Bill
> >>
> >> On Sat, Sep 23, 2023 at 6:23 PM Greg Harris
>   >>
> >> wrote:
> >>
> >>> Congratulations Justine!
> >>>
> >>> On Sat, Sep 23, 2023 at 5:49 AM Boudjelda Mohamed Said
> >>>  wrote:
> 
>  Congrats Justin !
> 
>  On Sat 23 Sep 2023 at 14:44, Randall Hauch 
>  wrote:
> 
> > Congratulations, Justine!
> >
> > On Sat, Sep 23, 2023 at 4:25 AM Kamal Chandraprakash <
> > kamal.chandraprak...@gmail.com> wrote:
> >
> >> Congrats Justine!
> >>
> >> On Sat, Sep 23, 2023, 13:28 Divij Vaidya <
> > divijvaidy...@gmail.com>
> > wrote:
> >>
> >>> Congratulations Justine!
> >>>
> >>> On Sat 23. Sep 2023 at 07:06, Chris Egerton <
> >>> fearthecel...@gmail.com>
> >>> wrote:
> >>>
>  Congrats Justine!
>  On Fri, Sep 22, 2023, 20:47 Guozhang Wang <
> > guozhang.wang...@gmail.com>
>  wrote:
> 
> > Congratulations!
> >
> > On Fri, Sep 22, 2023 at 8:44 PM Tzu-Li (Gordon) Tai <
> >>> tzuli...@apache.org
> >
> > wrote:
> >>
> >> Congratulations Justine!
> >>
> >> On Fri, Sep 22, 2023, 19:25 Philip Nee <
> > philip...@gmail.com>
> >> wrote:
> >>
> >>> Congrats Justine!
> >>>
> >>> On Fri, Sep 22, 2023 at 7:07 PM Luke Chen <
> >>> show...@gmail.com>
> >>> wrote:
> >>>
>  Hi, Everyone,
> 
>  Justine Olshan has been a Kafka committer since
>  Dec.
> >>> 2022.
> > She
> >>> has
> > been
>  very active and instrumental to the community since
> >>> becoming
> > a
> > committer.
>  It's my pleasure to announce that Justine is now a
> >>> member of
> >>> Kafka
> > PMC.
> 
>  Congratulations Justine!
> 
>  Luke
>  on behalf of Apache Kafka PMC
> 
> >>>
> >
> 
> >>>
> >>
> >
> >>>
> >
> >
> 
>
>

Re: [ANNOUNCE] New Kafka PMC Member: Justine Olshan

[Kirk True]

Congratulations Justine! Thanks for all your great work!

> On Sep 24, 2023, at 8:37 AM, John Roesler  wrote:
> 
> Congratulations, Justine!
> -John
> 
> On Sun, Sep 24, 2023, at 05:05, Mickael Maison wrote:
>> Congratulations Justine!
>> 
>> On Sun, Sep 24, 2023 at 5:04 AM Sophie Blee-Goldman
>>  wrote:
>>> 
>>> Congrats Justine!
>>> 
>>> On Sat, Sep 23, 2023, 4:36 PM Tom Bentley  wrote:
>>> 
 Congratulations!
 
 On Sun, 24 Sept 2023 at 12:32, Satish Duggana 
 wrote:
 
> Congratulations Justine!!
> 
> On Sat, 23 Sept 2023 at 15:46, Bill Bejeck  wrote:
>> 
>> Congrats Justine!
>> 
>> -Bill
>> 
>> On Sat, Sep 23, 2023 at 6:23 PM Greg Harris
 > 
>> wrote:
>> 
>>> Congratulations Justine!
>>> 
>>> On Sat, Sep 23, 2023 at 5:49 AM Boudjelda Mohamed Said
>>>  wrote:
 
 Congrats Justin !
 
 On Sat 23 Sep 2023 at 14:44, Randall Hauch 
 wrote:
 
> Congratulations, Justine!
> 
> On Sat, Sep 23, 2023 at 4:25 AM Kamal Chandraprakash <
> kamal.chandraprak...@gmail.com> wrote:
> 
>> Congrats Justine!
>> 
>> On Sat, Sep 23, 2023, 13:28 Divij Vaidya <
> divijvaidy...@gmail.com>
> wrote:
>> 
>>> Congratulations Justine!
>>> 
>>> On Sat 23. Sep 2023 at 07:06, Chris Egerton <
>>> fearthecel...@gmail.com>
>>> wrote:
>>> 
 Congrats Justine!
 On Fri, Sep 22, 2023, 20:47 Guozhang Wang <
> guozhang.wang...@gmail.com>
 wrote:
 
> Congratulations!
> 
> On Fri, Sep 22, 2023 at 8:44 PM Tzu-Li (Gordon) Tai <
>>> tzuli...@apache.org
> 
> wrote:
>> 
>> Congratulations Justine!
>> 
>> On Fri, Sep 22, 2023, 19:25 Philip Nee <
> philip...@gmail.com>
>> wrote:
>> 
>>> Congrats Justine!
>>> 
>>> On Fri, Sep 22, 2023 at 7:07 PM Luke Chen <
>>> show...@gmail.com>
>>> wrote:
>>> 
 Hi, Everyone,
 
 Justine Olshan has been a Kafka committer since
 Dec.
>>> 2022.
> She
>>> has
> been
 very active and instrumental to the community since
>>> becoming
> a
> committer.
 It's my pleasure to announce that Justine is now a
>>> member of
>>> Kafka
> PMC.
 
 Congratulations Justine!
 
 Luke
 on behalf of Apache Kafka PMC
 
>>> 
> 
 
>>> 
>> 
> 
>>> 
> 
> 
 

Re: [ANNOUNCE] New Kafka PMC Member: Justine Olshan

[John Roesler]

Congratulations, Justine!
-John

On Sun, Sep 24, 2023, at 05:05, Mickael Maison wrote:
> Congratulations Justine!
>
> On Sun, Sep 24, 2023 at 5:04 AM Sophie Blee-Goldman
>  wrote:
>>
>> Congrats Justine!
>>
>> On Sat, Sep 23, 2023, 4:36 PM Tom Bentley  wrote:
>>
>> > Congratulations!
>> >
>> > On Sun, 24 Sept 2023 at 12:32, Satish Duggana 
>> > wrote:
>> >
>> > > Congratulations Justine!!
>> > >
>> > > On Sat, 23 Sept 2023 at 15:46, Bill Bejeck  wrote:
>> > > >
>> > > > Congrats Justine!
>> > > >
>> > > > -Bill
>> > > >
>> > > > On Sat, Sep 23, 2023 at 6:23 PM Greg Harris
>> > > > > >
>> > > > wrote:
>> > > >
>> > > > > Congratulations Justine!
>> > > > >
>> > > > > On Sat, Sep 23, 2023 at 5:49 AM Boudjelda Mohamed Said
>> > > > >  wrote:
>> > > > > >
>> > > > > > Congrats Justin !
>> > > > > >
>> > > > > > On Sat 23 Sep 2023 at 14:44, Randall Hauch 
>> > wrote:
>> > > > > >
>> > > > > > > Congratulations, Justine!
>> > > > > > >
>> > > > > > > On Sat, Sep 23, 2023 at 4:25 AM Kamal Chandraprakash <
>> > > > > > > kamal.chandraprak...@gmail.com> wrote:
>> > > > > > >
>> > > > > > > > Congrats Justine!
>> > > > > > > >
>> > > > > > > > On Sat, Sep 23, 2023, 13:28 Divij Vaidya <
>> > > divijvaidy...@gmail.com>
>> > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > > Congratulations Justine!
>> > > > > > > > >
>> > > > > > > > > On Sat 23. Sep 2023 at 07:06, Chris Egerton <
>> > > > > fearthecel...@gmail.com>
>> > > > > > > > > wrote:
>> > > > > > > > >
>> > > > > > > > > > Congrats Justine!
>> > > > > > > > > > On Fri, Sep 22, 2023, 20:47 Guozhang Wang <
>> > > > > > > guozhang.wang...@gmail.com>
>> > > > > > > > > > wrote:
>> > > > > > > > > >
>> > > > > > > > > > > Congratulations!
>> > > > > > > > > > >
>> > > > > > > > > > > On Fri, Sep 22, 2023 at 8:44 PM Tzu-Li (Gordon) Tai <
>> > > > > > > > > tzuli...@apache.org
>> > > > > > > > > > >
>> > > > > > > > > > > wrote:
>> > > > > > > > > > > >
>> > > > > > > > > > > > Congratulations Justine!
>> > > > > > > > > > > >
>> > > > > > > > > > > > On Fri, Sep 22, 2023, 19:25 Philip Nee <
>> > > philip...@gmail.com>
>> > > > > > > > wrote:
>> > > > > > > > > > > >
>> > > > > > > > > > > > > Congrats Justine!
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > On Fri, Sep 22, 2023 at 7:07 PM Luke Chen <
>> > > > > show...@gmail.com>
>> > > > > > > > > wrote:
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > > Hi, Everyone,
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > Justine Olshan has been a Kafka committer since
>> > Dec.
>> > > > > 2022.
>> > > > > > > She
>> > > > > > > > > has
>> > > > > > > > > > > been
>> > > > > > > > > > > > > > very active and instrumental to the community since
>> > > > > becoming
>> > > > > > > a
>> > > > > > > > > > > committer.
>> > > > > > > > > > > > > > It's my pleasure to announce that Justine is now a
>> > > > > member of
>> > > > > > > > > Kafka
>> > > > > > > > > > > PMC.
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > Congratulations Justine!
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > Luke
>> > > > > > > > > > > > > > on behalf of Apache Kafka PMC
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > >
>> > >
>> > >
>> >

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

[Apache Jenkins Server]

See 

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

[Federico Valeri]

Hi Satish, I did the following to verify the release:

- Verified signature and checksum
- Built from source with Java 17 and Scala 2.13
- Ran all unit and integration tests
- Spot checked release notes and documentation
- Ran a custom client using staging artifacts on a 3-nodes cluster
- Tested tiered storage with one of the available RSM implementations

+1 (non binding)

Thanks
Fede


On Sun, Sep 24, 2023 at 8:49 AM Luke Chen  wrote:
>
> Hi Satish,
>
> I verified with:
> 1. Ran quick start in KRaft for scala 2.12 artifact
> 2. Making sure the checksum are correct
> 3. Browsing release notes, documents, javadocs, protocols.
>
> I filed KAFKA-15491 for
> log output improvement while testing stream application.
> It won't be blocker in v3.6.0.
>
> For KAFKA-15489 , I'm
> fine if we decide to fix it in v3.6.1/v3.7.0.
>
> +1 (binding) from me.
>
> Thank you.
> Luke
>
> On Sun, Sep 24, 2023 at 3:38 AM Ismael Juma  wrote:
>
> > Given that this is not a regression and there have been no reports for over
> > a year, I think it's ok for this to land in 3.6.1.
> >
> > Ismael
> >
> > On Sat, Sep 23, 2023 at 9:32 AM Satish Duggana 
> > wrote:
> >
> > > Thanks Luke for reporting KRaft issue[1].
> > >
> > > I am not sure whether it is a release blocker for 3.6.0. Need input
> > > from other KRaft experts also to finalize the decision. Even if we
> > > adopt a fix, do not we need to bake it for some time before it is
> > > pushed to production to avoid any regressions as this change is in the
> > > critical paths?
> > >
> > > 1. https://issues.apache.org/jira/browse/KAFKA-15489
> > >
> > > Thanks,
> > > Satish.
> > >
> > > On Sat, 23 Sept 2023 at 03:08, Luke Chen  wrote:
> > > >
> > > > Hi Satish,
> > > >
> > > > I found the current KRaft implementation will have "split brain" issue
> > > when
> > > > network partition happens, which will cause inconsistent metadata
> > > returned
> > > > from the controller.
> > > > Filed KAFKA-15489 
> > > for
> > > > this issue, and PR  is
> > ready
> > > > for review.
> > > >
> > > > Even though this is not a regression issue (this has already existed
> > > since
> > > > the 1st release of KRaft feature), I think this is an important issue
> > > since
> > > > KRaft is announced production ready.
> > > > Not sure what other people's thoughts are.
> > > >
> > > > Thank you.
> > > > Luke
> > > >
> > > > On Thu, Sep 21, 2023 at 6:33 PM Josep Prat  > >
> > > > wrote:
> > > >
> > > > > Hi Satish,
> > > > >
> > > > > I ran the following validation steps:
> > > > > - Built from source with Java 11 and Scala 2.13
> > > > > - Verified Signatures and hashes of the artifacts generated
> > > > > - Navigated through Javadoc including links to JDK classes
> > > > > - Run the unit tests
> > > > > - Run integration tests
> > > > > - Run the quickstart in KRaft and Zookeeper mode
> > > > >
> > > > >
> > > > > I +1 this release (non-binding)
> > > > >
> > > > > Thanks for your efforts!
> > > > >
> > > > > On Thu, Sep 21, 2023 at 2:59 AM Satish Duggana <
> > > satish.dugg...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Thanks Greg for verifying the release including the earlier
> > > > > > blocker(KAFKA-15473) verification.
> > > > > >
> > > > > > ~Satish.
> > > > > >
> > > > > > On Wed, 20 Sept 2023 at 22:30, Greg Harris
> > >  > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > I verified the functionality of KIP-898 and the recent fix for
> > > > > > > KAFKA-15473 with the following steps:
> > > > > > >
> > > > > > > 1. I started a 3.5.1 broker, and a 3.5.1 worker with most (>400)
> > > > > > > publicly available plugins installed
> > > > > > > 2. I captured the output of /connector-plugins
> > > > > > > 3. I upgraded the worker to 3.6.0-rc1
> > > > > > > 4. I captured the output of /connector-plugins with various
> > > settings
> > > > > > > of plugin.discovery
> > > > > > > 5. I ran the migration script to add manifests to my plugins
> > > > > > > 6. I captured the output of /connector-plugins with various
> > > settings
> > > > > > > of plugin.discovery
> > > > > > > 7. I downgraded the worker to 3.5.1
> > > > > > > 8. I diffed the output of /connector-plugins across the different
> > > > > > > cases and observed the expected changes.
> > > > > > > a. When plugins are migrated for 3.6.0, all modes produce
> > > identical
> > > > > > > results.
> > > > > > > b. When plugins are not migrated for 3.6.0, only_scan and
> > > > > > > hybrid_warn produce identical results, hybrid_fail crashes, and
> > > > > > > service_load is missing plugins
> > > > > > > c. When upgrading from 3.5.1 I see that plugins with invalid
> > > > > > > constructors are hidden, AK plugins now have versions,
> > > multi-interface
> > > > > > > plugins now show each interface 

[jira] [Created] (KAFKA-15494) Remove deprecation call of task registration of Gradle on build.gradle and use tasks.register instead

[Said BOUDJELDA (Jira)]

Said BOUDJELDA created KAFKA-15494:
--

 Summary: Remove deprecation call of task registration of Gradle on 
build.gradle and use tasks.register instead
 Key: KAFKA-15494
 URL: https://issues.apache.org/jira/browse/KAFKA-15494
 Project: Kafka
  Issue Type: Improvement
Reporter: Said BOUDJELDA
Assignee: Said BOUDJELDA


On the purpose of preparing the future upgrades of Gradle wrapper, we need to 
get ride of the deprecated  calls of certains methods as tasks registrations, 
this will make the future upgrades to *Gradle 9* where plenty of methods are 
marked for removal for this future big release, that will for sure brings 
support for *JDK 21* 

 

an exemple of deprecated usage of task registration

 
{code:java}

task aggregatedJavadoc(type: Javadoc, dependsOn: compileJava) {
  def projectsWithJavadoc = subprojects.findAll { it.javadoc.enabled }
  source = projectsWithJavadoc.collect { it.sourceSets.main.allJava }
  classpath = files(projectsWithJavadoc.collect { 
it.sourceSets.main.compileClasspath })
  includes = projectsWithJavadoc.collectMany { it.javadoc.getIncludes() }
  excludes = projectsWithJavadoc.collectMany { it.javadoc.getExcludes() }

  options.charSet = 'UTF-8'
  options.docEncoding = 'UTF-8'
  options.encoding = 'UTF-8'
  // Turn off doclint for now, see 
https://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html for 
rationale
  options.addStringOption('Xdoclint:none', '-quiet')

  // The URL structure was changed to include the locale after Java 8
  if (JavaVersion.current().isJava11Compatible())
options.links 
"https://docs.oracle.com/en/java/javase/${JavaVersion.current().majorVersion}/docs/api/"
  else
options.links "https://docs.oracle.com/javase/8/docs/api/;
}
 {code}
 

 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-15493) Ensure system tests work with Java 21

[Ismael Juma (Jira)]

Ismael Juma created KAFKA-15493:
---

 Summary: Ensure system tests work with Java 21
 Key: KAFKA-15493
 URL: https://issues.apache.org/jira/browse/KAFKA-15493
 Project: Kafka
  Issue Type: Improvement
Reporter: Ismael Juma
 Fix For: 3.7.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-15492) Enable spotbugs when building with Java 21

[Ismael Juma (Jira)]

Ismael Juma created KAFKA-15492:
---

 Summary: Enable spotbugs when building with Java 21
 Key: KAFKA-15492
 URL: https://issues.apache.org/jira/browse/KAFKA-15492
 Project: Kafka
  Issue Type: Improvement
Reporter: Ismael Juma


The latest version of spotbugs (4.7.3) doesn't support Java 21. In order not to 
delay Java 21 support, we disabled spotbugs when building with Java 21. This 
should be reverted once we upgrade to a version of spotbugs that supports Java 
21.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [ANNOUNCE] New Kafka PMC Member: Justine Olshan

[Mickael Maison]

Congratulations Justine!

On Sun, Sep 24, 2023 at 5:04 AM Sophie Blee-Goldman
 wrote:
>
> Congrats Justine!
>
> On Sat, Sep 23, 2023, 4:36 PM Tom Bentley  wrote:
>
> > Congratulations!
> >
> > On Sun, 24 Sept 2023 at 12:32, Satish Duggana 
> > wrote:
> >
> > > Congratulations Justine!!
> > >
> > > On Sat, 23 Sept 2023 at 15:46, Bill Bejeck  wrote:
> > > >
> > > > Congrats Justine!
> > > >
> > > > -Bill
> > > >
> > > > On Sat, Sep 23, 2023 at 6:23 PM Greg Harris
> >  > > >
> > > > wrote:
> > > >
> > > > > Congratulations Justine!
> > > > >
> > > > > On Sat, Sep 23, 2023 at 5:49 AM Boudjelda Mohamed Said
> > > > >  wrote:
> > > > > >
> > > > > > Congrats Justin !
> > > > > >
> > > > > > On Sat 23 Sep 2023 at 14:44, Randall Hauch 
> > wrote:
> > > > > >
> > > > > > > Congratulations, Justine!
> > > > > > >
> > > > > > > On Sat, Sep 23, 2023 at 4:25 AM Kamal Chandraprakash <
> > > > > > > kamal.chandraprak...@gmail.com> wrote:
> > > > > > >
> > > > > > > > Congrats Justine!
> > > > > > > >
> > > > > > > > On Sat, Sep 23, 2023, 13:28 Divij Vaidya <
> > > divijvaidy...@gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Congratulations Justine!
> > > > > > > > >
> > > > > > > > > On Sat 23. Sep 2023 at 07:06, Chris Egerton <
> > > > > fearthecel...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Congrats Justine!
> > > > > > > > > > On Fri, Sep 22, 2023, 20:47 Guozhang Wang <
> > > > > > > guozhang.wang...@gmail.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Congratulations!
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Sep 22, 2023 at 8:44 PM Tzu-Li (Gordon) Tai <
> > > > > > > > > tzuli...@apache.org
> > > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Congratulations Justine!
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, Sep 22, 2023, 19:25 Philip Nee <
> > > philip...@gmail.com>
> > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Congrats Justine!
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Fri, Sep 22, 2023 at 7:07 PM Luke Chen <
> > > > > show...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi, Everyone,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Justine Olshan has been a Kafka committer since
> > Dec.
> > > > > 2022.
> > > > > > > She
> > > > > > > > > has
> > > > > > > > > > > been
> > > > > > > > > > > > > > very active and instrumental to the community since
> > > > > becoming
> > > > > > > a
> > > > > > > > > > > committer.
> > > > > > > > > > > > > > It's my pleasure to announce that Justine is now a
> > > > > member of
> > > > > > > > > Kafka
> > > > > > > > > > > PMC.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Congratulations Justine!
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Luke
> > > > > > > > > > > > > > on behalf of Apache Kafka PMC
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > >
> > >
> > >
> >

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

[Luke Chen]

Hi Satish,

I verified with:
1. Ran quick start in KRaft for scala 2.12 artifact
2. Making sure the checksum are correct
3. Browsing release notes, documents, javadocs, protocols.

I filed KAFKA-15491 for
log output improvement while testing stream application.
It won't be blocker in v3.6.0.

For KAFKA-15489 , I'm
fine if we decide to fix it in v3.6.1/v3.7.0.

+1 (binding) from me.

Thank you.
Luke

On Sun, Sep 24, 2023 at 3:38 AM Ismael Juma  wrote:

> Given that this is not a regression and there have been no reports for over
> a year, I think it's ok for this to land in 3.6.1.
>
> Ismael
>
> On Sat, Sep 23, 2023 at 9:32 AM Satish Duggana 
> wrote:
>
> > Thanks Luke for reporting KRaft issue[1].
> >
> > I am not sure whether it is a release blocker for 3.6.0. Need input
> > from other KRaft experts also to finalize the decision. Even if we
> > adopt a fix, do not we need to bake it for some time before it is
> > pushed to production to avoid any regressions as this change is in the
> > critical paths?
> >
> > 1. https://issues.apache.org/jira/browse/KAFKA-15489
> >
> > Thanks,
> > Satish.
> >
> > On Sat, 23 Sept 2023 at 03:08, Luke Chen  wrote:
> > >
> > > Hi Satish,
> > >
> > > I found the current KRaft implementation will have "split brain" issue
> > when
> > > network partition happens, which will cause inconsistent metadata
> > returned
> > > from the controller.
> > > Filed KAFKA-15489 
> > for
> > > this issue, and PR  is
> ready
> > > for review.
> > >
> > > Even though this is not a regression issue (this has already existed
> > since
> > > the 1st release of KRaft feature), I think this is an important issue
> > since
> > > KRaft is announced production ready.
> > > Not sure what other people's thoughts are.
> > >
> > > Thank you.
> > > Luke
> > >
> > > On Thu, Sep 21, 2023 at 6:33 PM Josep Prat  >
> > > wrote:
> > >
> > > > Hi Satish,
> > > >
> > > > I ran the following validation steps:
> > > > - Built from source with Java 11 and Scala 2.13
> > > > - Verified Signatures and hashes of the artifacts generated
> > > > - Navigated through Javadoc including links to JDK classes
> > > > - Run the unit tests
> > > > - Run integration tests
> > > > - Run the quickstart in KRaft and Zookeeper mode
> > > >
> > > >
> > > > I +1 this release (non-binding)
> > > >
> > > > Thanks for your efforts!
> > > >
> > > > On Thu, Sep 21, 2023 at 2:59 AM Satish Duggana <
> > satish.dugg...@gmail.com>
> > > > wrote:
> > > >
> > > > > Thanks Greg for verifying the release including the earlier
> > > > > blocker(KAFKA-15473) verification.
> > > > >
> > > > > ~Satish.
> > > > >
> > > > > On Wed, 20 Sept 2023 at 22:30, Greg Harris
> >  > > > >
> > > > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > I verified the functionality of KIP-898 and the recent fix for
> > > > > > KAFKA-15473 with the following steps:
> > > > > >
> > > > > > 1. I started a 3.5.1 broker, and a 3.5.1 worker with most (>400)
> > > > > > publicly available plugins installed
> > > > > > 2. I captured the output of /connector-plugins
> > > > > > 3. I upgraded the worker to 3.6.0-rc1
> > > > > > 4. I captured the output of /connector-plugins with various
> > settings
> > > > > > of plugin.discovery
> > > > > > 5. I ran the migration script to add manifests to my plugins
> > > > > > 6. I captured the output of /connector-plugins with various
> > settings
> > > > > > of plugin.discovery
> > > > > > 7. I downgraded the worker to 3.5.1
> > > > > > 8. I diffed the output of /connector-plugins across the different
> > > > > > cases and observed the expected changes.
> > > > > > a. When plugins are migrated for 3.6.0, all modes produce
> > identical
> > > > > > results.
> > > > > > b. When plugins are not migrated for 3.6.0, only_scan and
> > > > > > hybrid_warn produce identical results, hybrid_fail crashes, and
> > > > > > service_load is missing plugins
> > > > > > c. When upgrading from 3.5.1 I see that plugins with invalid
> > > > > > constructors are hidden, AK plugins now have versions,
> > multi-interface
> > > > > > plugins now show each interface type, and plugins using
> > AppInfoParser
> > > > > > change versions.
> > > > > > d. The startup logs now include descriptive errors for
> invalid
> > > > > > plugins that otherwise would have been thrown at runtime
> > > > > > d. The fix for KAFKA-15473 prevents duplicates
> > > > > > e. The output for 3.5.1 after downgrading is identical to
> > before.
> > > > > >
> > > > > > +1 (non-binding)
> > > > > >
> > > > > > Thanks Satish for running the release!
> > > > > >
> > > > > > On Wed, Sep 20, 2023 at 8:36 AM Divij Vaidya 
> > > > wrote:
> > > > > > >
> > > > > > > Hey Satish
> > > > > > >
> > > > > > > My comments about documentation misses from RC0 vote thread [1]
> > 

[jira] [Created] (KAFKA-15491) RackId doesn't exist while running WordCountDemo

[Luke Chen (Jira)]

Luke Chen created KAFKA-15491:
-

 Summary: RackId doesn't exist while running WordCountDemo
 Key: KAFKA-15491
 URL: https://issues.apache.org/jira/browse/KAFKA-15491
 Project: Kafka
  Issue Type: Bug
  Components: streams
Reporter: Luke Chen


While running the WordCountDemo following the 
[docs|https://kafka.apache.org/documentation/streams/quickstart], I saw the 
following error logs in the stream application output. Though everything still 
works fine, it'd be better there are no ERROR logs in the demo app.


{code:java}
[2023-09-24 14:15:11,723] ERROR RackId doesn't exist for process 
e2391098-23e8-47eb-8d5e-ff6e697c33f5 and consumer 
streams-wordcount-e2391098-23e8-47eb-8d5e-ff6e697c33f5-StreamThread-1-consumer-adae58be-f5f5-429b-a2b4-67bf732726e8
 (org.apache.kafka.streams.processor.internals.assignment.RackAwareTaskAssignor)
[2023-09-24 14:15:11,757] ERROR RackId doesn't exist for process 
e2391098-23e8-47eb-8d5e-ff6e697c33f5 and consumer 
streams-wordcount-e2391098-23e8-47eb-8d5e-ff6e697c33f5-StreamThread-1-consumer-adae58be-f5f5-429b-a2b4-67bf732726e8
 (org.apache.kafka.streams.processor.internals.assignment.RackAwareTaskAssignor)
{code}




--
This message was sent by Atlassian Jira
(v8.20.10#820010)