Kafka

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.duggana@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 <greg.harris@aiven.io.invalid> > 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 i...

I am using Kafka broker 2.8.1 (from AWS MSK) with Kafka clients and Kafka stream 3.5.1. I am observing that whenever some rolling upgrade is done on AWS MSK our stream application reaches an error state. I get the below exception on trying to query the state store caused by: java.lang.IllegalStateException: KafkaStreams is not running. State is ERROR. at org.apache.kafka.streams.KafkaStreams.validateIsRunningOrRebalancing(KafkaStreams.java:381) at org.apache.kafka.streams.KafkaStreams.queryMetadataForKey(KafkaStreams.java:1663) at org.springframework.cloud.stream.binder.kafka.streams.InteractiveQueryService.lambda$getHostInfo$2(InteractiveQueryService.java:227) Can someone let me know what the recommended way we can keep the stream application running whenever some rolling upgrade/restart of brokers is done in the background?

Thanks Greg for verifying the release including the earlier blocker(KAFKA-15473) verification. ~Satish. On Wed, 20 Sept 2023 at 22:30, Greg Harris <greg.harris@aiven.io.invalid> 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. Whe...

Hi Divij, Thanks for calling out documentation issues. Some of them are being addressed in the existing documentation PRs. We will keep addressing the remaining documentation issues by making respective changes in kafka-site repo for 3.6.0 release. I think documentation is important but I do not consider documentation issues as release blockers. I want others to review and test the release candidate sooner to finalize the RC for 3.6.0 release. ~Satish. On Wed, 20 Sept 2023 at 21:04, Divij Vaidya < divijv@apache.org > wrote: > Hey Satish > > My comments about documentation misses from RC0 vote thread [1] are > still not addressed (such as missing metric documentation, formatting > problems etc). Could you please mention why we shouldn't consider them > as blockers to make RC1 as the final release? > > [1] https://lists.apache.org/thread/cokoxzd0jtgjtrlxoq7kkzmvpm75381t > > On Wed, Sep 20, 2023 at 4:53 PM Satish Duggana ...

My apologies; both classes are in the server-common...-test jar. Both issues can be closed. ________________________________ From: Gary Russell < grussell@vmware.com > Sent: Wednesday, September 20, 2023 3:56 PM To: users@kafka.apache.org < users@kafka.apache.org >; dev < dev@kafka.apache.org > Subject: Re: [kafka-clients] [VOTE] 3.6.0 RC1 I have lowered the priority because I found a work around, but it's still bad practice for a public class to depend on a class that is not published anywhere. This is similar to [2], which has been open for months. [1]: https://issues.apache.org/jira/browse/KAFKA-15482 [2]: https://issues.apache.org/jira/browse/KAFKA-15092 ________________________________ From: Gary Russell < grussell@vmware.com > Sent: Wednesday, September 20, 2023 3:36 PM To: users@kafka.apache.org < users@kafka.apache.org >; dev < dev@kafka.apache.org > Subject: Re: [kafka-clients] [VOTE] 3.6.0 RC1 This is a blo...

I have lowered the priority because I found a work around, but it's still bad practice for a public class to depend on a class that is not published anywhere. This is similar to [2], which has been open for months. [1]: https://issues.apache.org/jira/browse/KAFKA-15482 [2]: https://issues.apache.org/jira/browse/KAFKA-15092 ________________________________ From: Gary Russell < grussell@vmware.com > Sent: Wednesday, September 20, 2023 3:36 PM To: users@kafka.apache.org < users@kafka.apache.org >; dev < dev@kafka.apache.org > Subject: Re: [kafka-clients] [VOTE] 3.6.0 RC1 This is a blocker for me [1]. https://issues.apache.org/jira/browse/KAFKA-15482 ________________________________ From: Greg Harris <greg.harris@aiven.io.INVALID> Sent: Wednesday, September 20, 2023 12:45 PM To: users@kafka.apache.org < users@kafka.apache.org > Cc: dev < dev@kafka.apache.org >; kafka-clients@googlegroups.com < kafka-clients@googlegro...

This is a blocker for me [1]. https://issues.apache.org/jira/browse/KAFKA-15482 ________________________________ From: Greg Harris <greg.harris@aiven.io.INVALID> Sent: Wednesday, September 20, 2023 12:45 PM To: users@kafka.apache.org < users@kafka.apache.org > Cc: dev < dev@kafka.apache.org >; kafka-clients@googlegroups.com < kafka-clients@googlegroups.com > Subject: Re: [kafka-clients] [VOTE] 3.6.0 RC1 !! External Email 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...