Re: [VOTE] 3.1.1 RC1

2022-05-04 Thread Luke Chen
Hi Tom, I did: 1. check the signature and checksums 2. ran quick start with java17 + sacla2.12 3. browse java docs/documentations +1 (non-binding) Thanks for running the release. Luke On Thu, May 5, 2022 at 12:43 AM Bill Bejeck wrote: > Hi Tom, > > Thanks for running the release! > > I did

Re: [VOTE] 3.2.0 RC1

2022-05-04 Thread Luke Chen
Hi Bruno, I did: 1. check the signature and checksums 2. ran quick start with java17 + sacla2.12 3. browse java docs/documentations +1 (non-binding) Thanks for running the release. Luke On Thu, May 5, 2022 at 1:23 AM Mickael Maison wrote: > Hi Bruno, > > I checked signatures and checksums,

[jira] [Created] (KAFKA-13875) update docs to include topoicId for kafka-topics.sh --describe output

2022-05-04 Thread Luke Chen (Jira)
Luke Chen created KAFKA-13875: - Summary: update docs to include topoicId for kafka-topics.sh --describe output Key: KAFKA-13875 URL: https://issues.apache.org/jira/browse/KAFKA-13875 Project: Kafka

Re: [DISCUSS] KIP-833: Mark KRaft as Production Ready

2022-05-04 Thread Ismael Juma
Yes, all features supported by zk mode will be available in kraft mode in the 3.x series. Ismael On Wed, May 4, 2022, 5:28 PM Israel Ekpo wrote: > Ismael, > > I like the timeline. However, does this or will this also account for > features users rely on today in Zookeeper mode being available

[jira] [Created] (KAFKA-13874) Avoid synchronization in SocketServer metrics

2022-05-04 Thread Colin McCabe (Jira)
Colin McCabe created KAFKA-13874: Summary: Avoid synchronization in SocketServer metrics Key: KAFKA-13874 URL: https://issues.apache.org/jira/browse/KAFKA-13874 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-833: Mark KRaft as Production Ready

2022-05-04 Thread Israel Ekpo
Ismael, I like the timeline. However, does this or will this also account for features users rely on today in Zookeeper mode being available when Zookeeper is dropped? That’s my main concern On Wed, May 4, 2022 at 8:12 PM Ismael Juma wrote: > Hi Colin, > > Thanks for the KIP, this is

Re: [DISCUSS] KIP-833: Mark KRaft as Production Ready

2022-05-04 Thread Ismael Juma
Hi Colin, Thanks for the KIP, this is exciting. Trying to balance progress and compatibility, how about the following? 1. 3.3 (~August 2022): kraft is production ready for new clusters 2. 3.4 (~December 2022/January 2023): migration from zk to kraft is production ready and zk mode is deprecated

Re: [VOTE] 3.1.1 RC0

2022-05-04 Thread Ismael Juma
Hi Dongjoon, Any updates on your testing? Ismael On Fri, Apr 29, 2022, 12:04 PM Dongjoon Hyun wrote: > Thank you for the recommendation and the releasing, Tom and Ismael. > > There are some concerns about Apache Kafka 3.1.x still in the Apache Spark > dev mailing list. > > I'm going to

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

2022-05-04 Thread Apache Jenkins Server
See

Re: [DISCUSS] KIP-832 Allow creating a producer/consumer using a producer/consumer config

2022-05-04 Thread François Rosière
Hi all, KIP-832 has been created to allow implementing Spring managed interceptors for Producers and Consumers. At the moment, interceptors are given as configuration classes to the producer and consumer configurations. So, the idea here would be to create 2 new constructors to allow using a

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

2022-05-04 Thread Apache Jenkins Server
See

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

2022-05-04 Thread James Cheng
Hi Luke, Thanks for adding RemainingSegmentsToRecovery. Another thought: different topics can have different segment sizes. I don't know how common it is, but it is possible. Some topics might want small segment sizes to more granular expiration of data. The downside of

[jira] [Resolved] (KAFKA-13815) Avoid reinitialization for a replica that is being deleted

2022-05-04 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-13815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13815. - Fix Version/s: 3.3.0 Resolution: Fixed merged the PR to trunk > Avoid reinitialization for a

[jira] [Resolved] (KAFKA-13861) validateOnly request field does not work for CreatePartition requests in Kraft mode.

2022-05-04 Thread Akhilesh Chaganti (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-13861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhilesh Chaganti resolved KAFKA-13861. --- Resolution: Fixed > validateOnly request field does not work for CreatePartition

[DISCUSS] KIP-834: Pause / Resume KafkaStreams Topologies

2022-05-04 Thread Jim Hughes
Hi all, I have written up a KIP for adding the ability to pause and resume the processing of a topology in AK Streams. The KIP is here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211882832 Thanks in advance for your feedback! Cheers, Jim

[jira] [Created] (KAFKA-13873) Add ability to Pause / Resume KafkaStreams Topologies

2022-05-04 Thread Jim Hughes (Jira)
Jim Hughes created KAFKA-13873: -- Summary: Add ability to Pause / Resume KafkaStreams Topologies Key: KAFKA-13873 URL: https://issues.apache.org/jira/browse/KAFKA-13873 Project: Kafka Issue

Re: [VOTE] 3.2.0 RC1

2022-05-04 Thread Mickael Maison
Hi Bruno, I checked signatures and checksums, built from source, ran the unit tests and ran the quickstart. Javadocs and the website look fine too. +1 (binding) Thanks for running the release! Mickael On Wed, May 4, 2022 at 4:48 PM Bruno Cadonna wrote: > > Hello Kafka users, developers and

Re: [VOTE] 3.1.1 RC1

2022-05-04 Thread Bill Bejeck
Hi Tom, Thanks for running the release! I did the following checks: 1. Validated all the checksum and signatures 2. Built from source and ran the unit tests (Java 11) 3. Ran the quickstart and the Kafka Streams demo (Java 11) 4. Did a quick scan of the Javadoc and the documentation

[jira] [Created] (KAFKA-13872) Partitions are truncated when leader is replaced

2022-05-04 Thread Francois Visconte (Jira)
Francois Visconte created KAFKA-13872: - Summary: Partitions are truncated when leader is replaced Key: KAFKA-13872 URL: https://issues.apache.org/jira/browse/KAFKA-13872 Project: Kafka

Re: [VOTE] 3.2.0 RC1

2022-05-04 Thread Bruno Cadonna
Hello Kafka users, developers and client-developers, I've got a green build with unit/integration tests: https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.2/45/ Best, Bruno On 03.05.22 16:07, Bruno Cadonna wrote: Hello Kafka users, developers and client-developers, This is the second

Jenkins build is back to stable : Kafka » Kafka Branch Builder » 3.2 #45

2022-05-04 Thread Apache Jenkins Server
See

Re: [DISCUSS] KIP-833: Mark KRaft as Production Ready

2022-05-04 Thread Israel Ekpo
Thanks Colin for the update and clarification and the additional details you added. I second Igor's thoughts that we should not deprecate ZK before having feature parity. However, I think marking KRaft mode as production-ready is something that can be done independent of the status of feature

[jira] [Created] (KAFKA-13871) The documentation for the configuration item QUORUM_FETCH_TIMEOUT of the RaftConfig class is incorrect

2022-05-04 Thread yingquan he (Jira)
yingquan he created KAFKA-13871: --- Summary: The documentation for the configuration item QUORUM_FETCH_TIMEOUT of the RaftConfig class is incorrect Key: KAFKA-13871 URL:

Re: [VOTE] KIP-797: Accept duplicate listener on port for IPv4/IPv6

2022-05-04 Thread Igor Soarez
Hi Matthew, Thanks for submitting this KIP. This is a useful improvement. +1 non binding Best, -- Igor On Fri, Apr 22, 2022, at 12:01 PM, Tom Bentley wrote: > Hi Matthew, > > Thanks for the KIP, +1 (binding). > > Kind regards, > > Tom > > On Thu, 14 Apr 2022 at 12:15, Matthew de Detrich >

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

2022-05-04 Thread Luke Chen
Hi devs, If there are no other comments, I'll start a vote tomorrow. Thank you. Luke On Sun, May 1, 2022 at 5:08 PM Luke Chen wrote: > Hi James, > > Sorry for the late reply. > > Yes, this is a good point, to know how many segments to be recovered if > there are some large partitions. > I've

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

2022-05-04 Thread Igor Soarez
Hi Mickael, Thanks for writing this KIP. This would be a very useful improvement! -- Igor On Thu, Apr 7, 2022, at 10:16 AM, Mickael Maison wrote: > Hi, > > I wrote a small KIP to expose the total and usable space of logdirs > via the DescribeLogDirs API: >

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.2 #44

2022-05-04 Thread Apache Jenkins Server
See

Re: [DISCUSS] KIP-833: Mark KRaft as Production Ready

2022-05-04 Thread Igor Soarez
Hi Colin, It's very exciting to see KRaft ready for production! I see the value of marking it ready for production even with the current missing features. However, I'm worried about marking ZK mode as deprecated before these missing features are ready. It might be hard to estimate right now

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

2022-05-04 Thread Apache Jenkins Server
See

Re: [DISCUSS] KIP-833: Mark KRaft as Production Ready

2022-05-04 Thread Colin McCabe
On Tue, May 3, 2022, at 23:16, Colin McCabe wrote: > > To be clear, the proposal here is to have the bridge release be 3.4 and > then move on to a ZK-free 4.0. With a 3.5 release as an option (but not > requirement) if we can't finish everything in time after 3.4. So that > would be two more

Re: [DISCUSS] KIP-833: Mark KRaft as Production Ready

2022-05-04 Thread Colin McCabe
On Tue, May 3, 2022, at 19:32, Luke Chen wrote: > Hi Colin, > > So exciting to see the KIP to mark the Kraft production ready! > > Just one comment: We should make sure the period between ZK deprecation > (i.e. v3.4.0) to ZK removal (i.e. v4.0.0) is not too short. > Do we have any expectation for

Re: [DISCUSS] KIP-833: Mark KRaft as Production Ready

2022-05-04 Thread Colin McCabe
On Tue, May 3, 2022, at 20:48, Israel Ekpo wrote: > Hi Colin, > > Thanks for this KIP. I am very excited to see the proposal. > > A lot in the community have been asking when KRaft mode will be ready and I > think this KIP will provide a lot of the answers and guidance desperately > needed. > >