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

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 526225 lines...]
[2023-01-05T05:11:52.922Z] > Task :connect:json:testClasses UP-TO-DATE
[2023-01-05T05:11:52.922Z] > Task :connect:json:testJar
[2023-01-05T05:11:52.922Z] > Task :connect:json:testSrcJar
[2023-01-05T05:11:52.922Z] > Task :server-common:compileTestJava UP-TO-DATE
[2023-01-05T05:11:52.922Z] > Task :server-common:testClasses UP-TO-DATE
[2023-01-05T05:11:52.922Z] > Task :group-coordinator:compileTestJava NO-SOURCE
[2023-01-05T05:11:52.922Z] > Task :group-coordinator:testClasses UP-TO-DATE
[2023-01-05T05:11:52.922Z] > Task :metadata:compileTestJava UP-TO-DATE
[2023-01-05T05:11:52.922Z] > Task :metadata:testClasses UP-TO-DATE
[2023-01-05T05:11:52.922Z] > Task 
:clients:generateMetadataFileForMavenJavaPublication
[2023-01-05T05:11:52.922Z] > Task :streams:copyDependantLibs
[2023-01-05T05:11:52.922Z] > Task :streams:jar UP-TO-DATE
[2023-01-05T05:11:53.857Z] > Task 
:streams:generateMetadataFileForMavenJavaPublication
[2023-01-05T05:11:57.440Z] > Task :connect:api:javadoc
[2023-01-05T05:11:57.440Z] > Task :connect:api:copyDependantLibs UP-TO-DATE
[2023-01-05T05:11:57.440Z] > Task :connect:api:jar UP-TO-DATE
[2023-01-05T05:11:57.440Z] > Task 
:connect:api:generateMetadataFileForMavenJavaPublication
[2023-01-05T05:11:57.440Z] > Task :connect:json:copyDependantLibs UP-TO-DATE
[2023-01-05T05:11:57.440Z] > Task :connect:json:jar UP-TO-DATE
[2023-01-05T05:11:57.440Z] > Task 
:connect:json:generateMetadataFileForMavenJavaPublication
[2023-01-05T05:11:57.440Z] > Task 
:connect:json:publishMavenJavaPublicationToMavenLocal
[2023-01-05T05:11:57.440Z] > Task :connect:json:publishToMavenLocal
[2023-01-05T05:11:57.440Z] > Task :connect:api:javadocJar
[2023-01-05T05:11:57.440Z] > Task :connect:api:compileTestJava UP-TO-DATE
[2023-01-05T05:11:57.440Z] > Task :connect:api:testClasses UP-TO-DATE
[2023-01-05T05:11:57.440Z] > Task :connect:api:testJar
[2023-01-05T05:11:57.440Z] 
[2023-01-05T05:11:57.440Z] > Task :streams:javadoc
[2023-01-05T05:11:57.440Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/streams/src/main/java/org/apache/kafka/streams/processor/StreamPartitioner.java:54:
 warning - Tag @link: reference not found: 
org.apache.kafka.clients.producer.internals.DefaultPartitioner
[2023-01-05T05:11:57.440Z] 
[2023-01-05T05:11:57.440Z] > Task :connect:api:testSrcJar
[2023-01-05T05:11:57.440Z] > Task 
:connect:api:publishMavenJavaPublicationToMavenLocal
[2023-01-05T05:11:57.440Z] > Task :connect:api:publishToMavenLocal
[2023-01-05T05:11:57.440Z] 
[2023-01-05T05:11:57.440Z] > Task :clients:javadoc
[2023-01-05T05:11:57.440Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/clients/src/main/java/org/apache/kafka/common/security/oauthbearer/OAuthBearerLoginCallbackHandler.java:151:
 warning - Tag @link: reference not found: 
[2023-01-05T05:12:00.069Z] 
[2023-01-05T05:12:00.069Z] > Task :streams:javadoc
[2023-01-05T05:12:00.069Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:890:
 warning - Tag @link: reference not found: DefaultPartitioner
[2023-01-05T05:12:00.069Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:919:
 warning - Tag @link: reference not found: DefaultPartitioner
[2023-01-05T05:12:00.069Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:939:
 warning - Tag @link: reference not found: DefaultPartitioner
[2023-01-05T05:12:00.069Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:854:
 warning - Tag @link: reference not found: DefaultPartitioner
[2023-01-05T05:12:00.069Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:890:
 warning - Tag @link: reference not found: DefaultPartitioner
[2023-01-05T05:12:00.069Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:919:
 warning - Tag @link: reference not found: DefaultPartitioner
[2023-01-05T05:12:00.069Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/streams/src/main/java/org/apache/kafka/streams/kstream/KStream.java:939:
 warning - Tag @link: reference not found: DefaultPartitioner
[2023-01-05T05:12:00.069Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/streams/src/main/java/org/apache/kafka/streams/kstream/Produced.java:84:
 warning - Tag @link: reference not found: DefaultPartitioner
[2023-01-05T05:12:00.069Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk_2/streams/src/main/java/org/apache/kafka/streams/kstream/Produced.java:136:
 warning - Tag @link: reference not found: 

[jira] [Created] (KAFKA-14574) Add doc generation as part of the CI build process

[Satish Duggana (Jira)]

Satish Duggana created KAFKA-14574:
--

 Summary: Add doc generation as part of the CI build process
 Key: KAFKA-14574
 URL: https://issues.apache.org/jira/browse/KAFKA-14574
 Project: Kafka
  Issue Type: Improvement
Reporter: Satish Duggana


Add doc generation as part of the CI build process so that any doc generation 
errors are caught while build is generated.

https://github.com/apache/kafka/pull/13079#issuecomment-1371663717 



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

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.4 #28

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

[jira] [Resolved] (KAFKA-14571) ZkMetadataCache.getClusterMetadata is missing rack information in aliveNodes

[Ismael Juma (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-14571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ismael Juma resolved KAFKA-14571.
-
Resolution: Fixed

> ZkMetadataCache.getClusterMetadata is missing rack information in aliveNodes
> 
>
> Key: KAFKA-14571
> URL: https://issues.apache.org/jira/browse/KAFKA-14571
> Project: Kafka
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3
>Reporter: Edoardo Comar
>Assignee: Edoardo Comar
>Priority: Minor
> Fix For: 3.4.0, 3.3.3
>
>
> ZkMetadataCache.getClusterMetadata returns a Cluster object where the 
> aliveNodes are missing their rack info.
> when ZkMetadataCache updates the metadataSnapshot, includes the rack in 
> `aliveBrokers` but not in `aliveNodes` 



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

[jira] [Created] (KAFKA-14573) RoundRobinPartitioner doesn't work as expected with topic that has 6 partitions

[Stephane Maarek (Jira)]

Stephane Maarek created KAFKA-14573:
---

 Summary: RoundRobinPartitioner doesn't work as expected with topic 
that has 6 partitions
 Key: KAFKA-14573
 URL: https://issues.apache.org/jira/browse/KAFKA-14573
 Project: Kafka
  Issue Type: Bug
Affects Versions: 3.3.1
Reporter: Stephane Maarek
 Attachments: image-2023-01-04-20-15-43-039.png

Create a topic with 6 partitions (that's how the behavior is observed)
```
kafka-topics.sh --bootstrap-server localhost:9092 --topic test_topic --create 
--partitions 6
```

Start a consumer
```
kafka-console-consumer --bootstrap-server localhost:9092 --topic test_topic 
--formatter kafka.tools.DefaultMessageFormatter --property print.timestamp=true 
--property print.key=true --property print.value=true --property 
print.partition=true --from-beginning
```

Start a producer using `RoundRobinPartitioner`
```
kafka-console-producer.sh --bootstrap-server localhost:9092 --producer-property 
partitioner.class=org.apache.kafka.clients.producer.RoundRobinPartitioner 
--topic test_topic
```

And you will see only 3 partitions get produced to (not 6)

This doesn't happen with 3 partitions, 5, 7, 9 partitions (we get the expected 
behavior).

But with 6 it happens.

Verified to be like this on my colleague's computer too. 

 !image-2023-01-04-20-15-43-039.png! 



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

[jira] [Created] (KAFKA-14572) Migrate EmbeddedKafkaCluster used by Streams integration tests from EmbeddedZookeeper to KRaft

[Matthias J. Sax (Jira)]

Matthias J. Sax created KAFKA-14572:
---

 Summary: Migrate EmbeddedKafkaCluster used by Streams integration 
tests from EmbeddedZookeeper to KRaft
 Key: KAFKA-14572
 URL: https://issues.apache.org/jira/browse/KAFKA-14572
 Project: Kafka
  Issue Type: Test
  Components: streams, unit tests
Reporter: Matthias J. Sax
 Fix For: 4.0.0


ZK will be removed in 4.0, and we need to update our test to switch to ZK to 
KRaft.



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

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

[Apache Jenkins Server]

See 

Re: [DISCUSS] KIP-896: Remove old client protocol API versions in Kafka 4.0

[Ismael Juma]

Hi Viktor,

Thanks for the feedback. See inline.

I was gonna ask about whether you think it would be useful to automate
> protocol deprecation but I see you'll have a separate KIP for that so I'll
> just wait :).
>

With regards to the follow-up KIP, if you are interested in submitting
that, please go ahead. My high level idea was something like the following:


Starting with Apache Kafka 5.0, the broker only keeps the latest protocol
API version from the first release in previous major version series or a
minor release that is at least n years old, whichever is oldest. Reasonable
values for `n` could be `3` or `4`.

Let's assume `n` is 3 and we release Apache Kafka 5.0 4 years after Apache
Kafka 4.0, then we'd keep the highest protocol API version for each
protocol from Apache Kafka 4.0. However, if Apache Kafka 5.0 was released 2
years after Apache Kafka 4.0, then we'd pick the relevant 3.x release as
the baseline instead.

If you do decide to write the KIP, feel free to suggest what you think is
best, of course. With that said, let's leave further discussions on this
future KIP idea to the future KIP thread. :)

I see that in multiple places clients have older than baseline
> implementation. Would it make sense in your opinion to also document that
> those protocols below the baseline will be deprecated in 4.0 and possibly
> go away in next versions (with maybe the deprecation/removal automation)
>

I considered that, but I thought it would be handled more cleanly by the
mechanical policy of the future KIP while this KIP focuses only on what
happens in 4.0.

Ismael

On Wed, Jan 4, 2023 at 7:42 AM Viktor Somogyi-Vass
 wrote:

> Hi Ismael,
>
> I think this is a good idea, it can also simplify the code quite a bit.
> I was gonna ask about whether you think it would be useful to automate
> protocol deprecation but I see you'll have a separate KIP for that so I'll
> just wait :).
>
> I see that in multiple places clients have older than baseline
> implementation. Would it make sense in your opinion to also document that
> those protocols below the baseline will be deprecated in 4.0 and possibly
> go away in next versions (with maybe the deprecation/removal automation)?
>
> Viktor
>
> On Tue, Jan 3, 2023 at 5:18 PM Ismael Juma  wrote:
>
> > Hi all,
> >
> > I would like to start a discussion regarding the removal of very old
> client
> > protocol API versions in Apache Kafka 4.0 to improve maintainability &
> > supportability of Kafka. Please take a look at the proposal:
> >
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
> >
> > Ismael
> >
>

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

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 445456 lines...]
[2023-01-04T15:42:18.047Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testGetDataAndStat() PASSED
[2023-01-04T15:42:18.047Z] 
[2023-01-04T15:42:18.047Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testReassignPartitionsInProgress() STARTED
[2023-01-04T15:42:18.047Z] 
[2023-01-04T15:42:18.047Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testReassignPartitionsInProgress() PASSED
[2023-01-04T15:42:18.047Z] 
[2023-01-04T15:42:18.047Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testChrootExistsAndRootIsLocked() STARTED
[2023-01-04T15:42:19.239Z] 
[2023-01-04T15:42:19.239Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testChrootExistsAndRootIsLocked() PASSED
[2023-01-04T15:42:19.239Z] 
[2023-01-04T15:42:19.239Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testCreateTopLevelPaths() STARTED
[2023-01-04T15:42:19.239Z] 
[2023-01-04T15:42:19.239Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testCreateTopLevelPaths() PASSED
[2023-01-04T15:42:19.239Z] 
[2023-01-04T15:42:19.239Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > 
testGetAllTopicsInClusterDoesNotTriggerWatch() STARTED
[2023-01-04T15:42:19.239Z] 
[2023-01-04T15:42:19.239Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > 
testGetAllTopicsInClusterDoesNotTriggerWatch() PASSED
[2023-01-04T15:42:19.239Z] 
[2023-01-04T15:42:19.239Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testIsrChangeNotificationGetters() STARTED
[2023-01-04T15:42:20.522Z] 
[2023-01-04T15:42:20.522Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testIsrChangeNotificationGetters() PASSED
[2023-01-04T15:42:20.522Z] 
[2023-01-04T15:42:20.522Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testLogDirEventNotificationsDeletion() 
STARTED
[2023-01-04T15:42:20.522Z] 
[2023-01-04T15:42:20.522Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testLogDirEventNotificationsDeletion() PASSED
[2023-01-04T15:42:20.522Z] 
[2023-01-04T15:42:20.522Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testGetLogConfigs() STARTED
[2023-01-04T15:42:20.522Z] 
[2023-01-04T15:42:20.522Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testGetLogConfigs() PASSED
[2023-01-04T15:42:20.522Z] 
[2023-01-04T15:42:20.522Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testBrokerSequenceIdMethods() STARTED
[2023-01-04T15:42:20.522Z] 
[2023-01-04T15:42:20.522Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testBrokerSequenceIdMethods() PASSED
[2023-01-04T15:42:20.522Z] 
[2023-01-04T15:42:20.522Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testAclMethods() STARTED
[2023-01-04T15:42:21.457Z] 
[2023-01-04T15:42:21.457Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testAclMethods() PASSED
[2023-01-04T15:42:21.457Z] 
[2023-01-04T15:42:21.457Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testCreateSequentialPersistentPath() STARTED
[2023-01-04T15:42:21.457Z] 
[2023-01-04T15:42:21.457Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testCreateSequentialPersistentPath() PASSED
[2023-01-04T15:42:21.457Z] 
[2023-01-04T15:42:21.457Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testConditionalUpdatePath() STARTED
[2023-01-04T15:42:22.390Z] 
[2023-01-04T15:42:22.390Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testConditionalUpdatePath() PASSED
[2023-01-04T15:42:22.390Z] 
[2023-01-04T15:42:22.390Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testGetAllTopicsInClusterTriggersWatch() 
STARTED
[2023-01-04T15:42:22.390Z] 
[2023-01-04T15:42:22.390Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testGetAllTopicsInClusterTriggersWatch() 
PASSED
[2023-01-04T15:42:22.390Z] 
[2023-01-04T15:42:22.390Z] Gradle Test Run :core:integrationTest > Gradle Test 
Executor 171 > KafkaZkClientTest > testDeleteTopicZNode() STARTED
[2023-01-04T15:42:22.390Z] 
[2023-01-04T15:42:22.390Z] Gradle Test Run :core:integrationTest > Gradle Test 

Re: [DISCUSS] KIP-896: Remove old client protocol API versions in Kafka 4.0

[Viktor Somogyi-Vass]

Hi Ismael,

I think this is a good idea, it can also simplify the code quite a bit.
I was gonna ask about whether you think it would be useful to automate
protocol deprecation but I see you'll have a separate KIP for that so I'll
just wait :).

I see that in multiple places clients have older than baseline
implementation. Would it make sense in your opinion to also document that
those protocols below the baseline will be deprecated in 4.0 and possibly
go away in next versions (with maybe the deprecation/removal automation)?

Viktor

On Tue, Jan 3, 2023 at 5:18 PM Ismael Juma  wrote:

> Hi all,
>
> I would like to start a discussion regarding the removal of very old client
> protocol API versions in Apache Kafka 4.0 to improve maintainability &
> supportability of Kafka. Please take a look at the proposal:
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
>
> Ismael
>

[jira] [Created] (KAFKA-14571) ZkMetadataCache.getClusterMetadata is missing rack information for aliveNodes

[Edoardo Comar (Jira)]

Edoardo Comar created KAFKA-14571:
-

 Summary: ZkMetadataCache.getClusterMetadata is missing rack 
information for aliveNodes
 Key: KAFKA-14571
 URL: https://issues.apache.org/jira/browse/KAFKA-14571
 Project: Kafka
  Issue Type: Bug
  Components: core
Affects Versions: 3.3
Reporter: Edoardo Comar
Assignee: Edoardo Comar


ZkMetadataCache.getClusterMetadata returns a Cluster object where the 
aliveNodes are missing their rack info.

when ZkMetadataCache updates the metadataSnapshot, includes the rack in 
`aliveBrokers` but not in `aliveNodes` 



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

[jira] [Created] (KAFKA-14570) Problem description missing right parenthesis symbol

[iamazy (Jira)]

iamazy created KAFKA-14570:
--

 Summary: Problem description missing right parenthesis symbol
 Key: KAFKA-14570
 URL: https://issues.apache.org/jira/browse/KAFKA-14570
 Project: Kafka
  Issue Type: Improvement
  Components: clients
Reporter: iamazy


In 
org.apache.kafka.clients.FetchSessionHandler#verifyFullFetchResponsePartitions, 
the Problem description missing right parenthesis symbol.



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

Re: [VOTE] 3.3.2 RC1

[Satish Duggana]

Hi Chris,
Thanks for running the release.

+1 (binding)

- Verified signatures and artifacts
- Ran testAll/releaseTarGzAll successfully with no failures.
- Ran through quickstart of core/streams on builds generated from the tag.
- Ran a few internal apps targeting to topics on 3 node cluster.

On Wed, 4 Jan 2023 at 00:49, Manikumar  wrote:
>
> Hi Chris,
>
> +1 (binding)
>
> - verified the signatures, artifacts
> - ran the tests on the source archive
> - verified the quickstarts
>
> Thanks for running the release!
>
> Thanks,
> Manikumar
>
>
> On Fri, Dec 23, 2022 at 4:44 PM Federico Valeri  wrote:
> >
> > Hi, I did the following to validate the release:
> >
> > - Checksums and signatures ok
> > - Build from source using Java 17 and Scala 2.13 ok
> > - Unit and integration tests ok
> > - Quickstart in both ZK and KRaft modes ok
> > - Test app with staging Maven artifacts ok
> >
> > +1 (non binding)
> >
> > Thanks
> > Fede
> >
> > On Wed, Dec 21, 2022 at 11:21 PM Chris Egerton  
> > wrote:
> > >
> > > Hello Kafka users, developers and client-developers,
> > >
> > > This is the second candidate for release of Apache Kafka 3.3.2.
> > >
> > > This is a bugfix release with several fixes since the release of 3.3.1. A
> > > few of the major issues include:
> > >
> > > * KAFKA-14358 Users should not be able to create a regular topic name
> > > __cluster_metadata
> > > KAFKA-14379 Consumer should refresh preferred read replica on update
> > > metadata
> > > * KAFKA-13586 Prevent exception thrown during connector update from
> > > crashing distributed herder
> > >
> > >
> > > Release notes for the 3.3.2 release:
> > > https://home.apache.org/~cegerton/kafka-3.3.2-rc1/RELEASE_NOTES.html
> > >
> > > *** Please download, test and vote by Friday, January 6, 2023, 10pm UTC
> > > (this date is chosen to accommodate the various upcoming holidays that
> > > members of the community will be taking and give everyone enough time to
> > > test out the release candidate, without unduly delaying the release)
> > >
> > > 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/~cegerton/kafka-3.3.2-rc1/
> > >
> > > * Maven artifacts to be voted upon:
> > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > >
> > > * Javadoc:
> > > https://home.apache.org/~cegerton/kafka-3.3.2-rc1/javadoc/
> > >
> > > * Tag to be voted upon (off 3.3 branch) is the 3.3.2 tag:
> > > https://github.com/apache/kafka/releases/tag/3.3.2-rc1
> > >
> > > * Documentation:
> > > https://kafka.apache.org/33/documentation.html
> > >
> > > * Protocol:
> > > https://kafka.apache.org/33/protocol.html
> > >
> > > The most recent build has had test failures. These all appear to be due to
> > > flakiness, but it would be nice if someone more familiar with the failed
> > > tests could confirm this. I may update this thread with passing build 
> > > links
> > > if I can get one, or start a new release vote thread if test failures must
> > > be addressed beyond re-running builds until they pass.
> > >
> > > Unit/integration tests:
> > > https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.3/142/testReport/
> > >
> > > José, would it be possible to re-run the system tests for 3.3 on the 
> > > latest
> > > commit for 3.3 (e3212f2), and share the results on this thread?
> > >
> > > Cheers,
> > >
> > > Chris

[jira] [Created] (KAFKA-14569) Migrate EmbeddedKafkaCluster used by Connect integration tests from EmbeddedZookeeper to KRaft

[Yash Mayya (Jira)]

Yash Mayya created KAFKA-14569:
--

 Summary: Migrate EmbeddedKafkaCluster used by Connect integration 
tests from EmbeddedZookeeper to KRaft
 Key: KAFKA-14569
 URL: https://issues.apache.org/jira/browse/KAFKA-14569
 Project: Kafka
  Issue Type: Task
  Components: KafkaConnect
Reporter: Yash Mayya
Assignee: Yash Mayya


ZooKeeper mode is going to be deprecated in Apache Kafka 4.0. Connect currently 
uses an 
[EmbeddedKafkaCluster|https://github.com/apache/kafka/blob/b8ab09820cd96290176afd24cf7b03e7cda7f783/connect/runtime/src/test/java/org/apache/kafka/connect/util/clusters/EmbeddedKafkaCluster.java#L95]
 for integration tests that depends on an 
[EmbeddedZookeeper.|https://github.com/apache/kafka/blob/b8ab09820cd96290176afd24cf7b03e7cda7f783/connect/runtime/src/test/java/org/apache/kafka/connect/util/clusters/EmbeddedKafkaCluster.java#L147]
 This should be migrated to remove the ZooKeeper dependency, instead working in 
the KRaft mode (probably with co-located brokers and controllers). We could 
potentially leverage the existing test kit for KRaft clusters 
([https://github.com/apache/kafka/tree/b8ab09820cd96290176afd24cf7b03e7cda7f783/core/src/test/java/kafka/testkit)]
 which handles a bunch of stuff including the listeners configuration setup, 
formatting the metadata log directory, allowing usage of non-static random 
ports for `controller.quorum.voters`, initialization of the shared server(s), 
broker(s), and controller(s) etc.

 

One more thing to note is that some Connect integration tests currently use the 
`kafka.security.authorizer.AclAuthorizer` which requires ZooKeeper. These tests 
should be migrated to use the new authorizer from 
[KIP-801|https://cwiki.apache.org/confluence/display/KAFKA/KIP-801%3A+Implement+an+Authorizer+that+stores+metadata+in+__cluster_metadata]
 if we want to completely eliminate the dependency on ZooKeeper.



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

[jira] [Created] (KAFKA-14568) Move FetchDataInfo and related to storage module

[Federico Valeri (Jira)]

Federico Valeri created KAFKA-14568:
---

 Summary: Move FetchDataInfo and related to storage module
 Key: KAFKA-14568
 URL: https://issues.apache.org/jira/browse/KAFKA-14568
 Project: Kafka
  Issue Type: Sub-task
Reporter: Federico Valeri
 Fix For: 3.5.0






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