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

See

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

See

[GitHub] [kafka-site] satishd commented on a diff in pull request #547: Added a blog entry for 3.6.0 release

satishd commented on code in PR #547: URL: https://github.com/apache/kafka-site/pull/547#discussion_r1330833102 ## blog.html: ## @@ -22,6 +22,46 @@ Blog + + + +Apache Kafka

Re: [VOTE] 3.6.0 RC0

Hi David, Thanks for the update. Please get it reviewed sooner. I plan to create RC1 in the next 5 hrs. As it is not a release blocker, I will merge it if this PR is approved and jenkins job looks good within that time. Thanks, Satish. On Wed, 20 Sept 2023 at 01:42, David Arthur wrote: > > As

[GitHub] [kafka-site] satishd commented on a diff in pull request #547: Added a blog entry for 3.6.0 release

satishd commented on code in PR #547: URL: https://github.com/apache/kafka-site/pull/547#discussion_r1330823812 ## blog.html: ## @@ -22,6 +22,46 @@ Blog + + + +Apache Kafka

[GitHub] [kafka-site] satishd commented on a diff in pull request #547: Added a blog entry for 3.6.0 release

satishd commented on code in PR #547: URL: https://github.com/apache/kafka-site/pull/547#discussion_r1330802348 ## blog.html: ## @@ -22,6 +22,46 @@ Blog + + + +Apache Kafka

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

See

Re: [DISCUSS] KIP-966: Eligible Leader Replicas

Hi Calvin, Thanks for the explanations. I like the idea of using none, balanced, aggressive. We also had an offline discussion about why it is good to use a new config key (basically, so that we can deprecate the old one which had only false/true values in 4.0) With these changes, I am +1.

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

See

Re: [VOTE] 3.6.0 RC0

As part of validating this RC, I found that most of the ZK migration system tests were failing. I investigated this today and found that it was just problems in the test code. This is not a blocker, but since we're doing RC1, I'd like to include it https://github.com/apache/kafka/pull/14409 On

[GitHub] [kafka-site] jolshan commented on a diff in pull request #547: Added a blog entry for 3.6.0 release

jolshan commented on code in PR #547: URL: https://github.com/apache/kafka-site/pull/547#discussion_r1330577105 ## blog.html: ## @@ -22,6 +22,46 @@ Blog + + + +Apache Kafka

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

See

Re: [DISCUSS] KIP-979: Allow independently stop KRaft controllers or brokers

Thanks for the KIP, Hailey. It will be nice to provide some fine-grained control for when people running the broker and controller this way want to stop just one of them. One thing that occurs to me is that in a development environment someone might want to run multiple controllers and multiple

[jira] [Created] (KAFKA-15479) Remote log segments should be considered once during retention size breach

Kamal Chandraprakash created KAFKA-15479: Summary: Remote log segments should be considered once during retention size breach Key: KAFKA-15479 URL: https://issues.apache.org/jira/browse/KAFKA-15479

[DISCUSS] KIP-981: Manage Connect topics with custom implementation of Admin

Hi everyone, I want to start the discussion of the KIP-981 to extend Connect to use org.apache.kafka.clients.admin.ForwardingAdminClient instead of KafkaAdminClient https://cwiki.apache.org/confluence/display/KAFKA/KIP-981%3A+Manage+Connect+topics+with+custom+implementation+of+Admin Thanks for

[jira] [Created] (KAFKA-15478) Update connect to use ForwardingAdmin

Omnia Ibrahim created KAFKA-15478: - Summary: Update connect to use ForwardingAdmin Key: KAFKA-15478 URL: https://issues.apache.org/jira/browse/KAFKA-15478 Project: Kafka Issue Type: New

Re: [VOTE] 3.6.0 RC0

Hi All, I will start creating a new RC with the fix and send it for a vote by tomorrow as https://issues.apache.org/jira/browse/KAFKA-15473 is determined to be a release blocker. Thanks. Satish. On Tue, 19 Sept 2023 at 22:26, Satish Duggana wrote: > > Thanks Chris for your comment on the

Re: [VOTE] 3.6.0 RC0

Thanks Chris for your comment on the reported issue. ~Satish. On Tue, 19 Sept 2023 at 22:16, Chris Egerton wrote: > > Hi all, > > Given the regression raised by Greg Harris ( > https://issues.apache.org/jira/browse/KAFKA-15473) on the release thread, I > believe we should generate a new

Re: [VOTE] 3.6.0 RC0

Hi all, Given the regression raised by Greg Harris ( https://issues.apache.org/jira/browse/KAFKA-15473) on the release thread, I believe we should generate a new candidate with a fix. I'm -1 (binding) on this RC. Best, Chris On Tue, Sep 19, 2023 at 10:30 AM Christo Lolov wrote: > Heya, > >

[jira] [Resolved] (KAFKA-15473) Connect connector-plugins endpoint shows duplicate plugins

[ https://issues.apache.org/jira/browse/KAFKA-15473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15473. --- Fix Version/s: 3.7.0 (was: 3.6.0) Resolution: Fixed > Connect

[jira] [Resolved] (KAFKA-15463) StreamsException: Accessing from an unknown node

[ https://issues.apache.org/jira/browse/KAFKA-15463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Brutschy resolved KAFKA-15463. Resolution: Not A Problem > StreamsException: Accessing from an unknown node >

Re: Apache Kafka 3.6.0 release

Hi Satish, I think this qualifies as a blocker. This API has been around for years now and, while we don't document it as not exposing duplicates*, it has come with that implicit contract since its inception. More importantly, it has also never exposed plugins that cannot be used on the worker.

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

See

[jira] [Created] (KAFKA-15477) Kafka won't shutdown when deleting remote segment

Francois Visconte created KAFKA-15477: - Summary: Kafka won't shutdown when deleting remote segment Key: KAFKA-15477 URL: https://issues.apache.org/jira/browse/KAFKA-15477 Project: Kafka

Re: [VOTE] 3.6.0 RC0

Heya, I have compiled and ran the test target successfully for the 3.6.0-rc0 branch on: Java 11, Scala 2.13 - ARM Java 17, Scala 2.13 - ARM Java 20, Scala 2.18 - ARM Java 11, Scala 2.13 - Intel x86 Java 17, Scala 2.13 - Intel x86 Java 20, Scala 2.13 - Intel x86 I will update the Zookeeper KIP

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

Ok, great, that makes sense, Igor. Thanks. +1 (binding) on the KIP from me. Ron > On Sep 13, 2023, at 11:58 AM, Igor Soarez wrote: > > Hi Ron, > > Thanks for drilling down on this. I think the KIP isn't really clear here, > and the metadata caching section you quoted needs clarification. >

[GitHub] [kafka-site] divijvaidya commented on a diff in pull request #547: Added a blog entry for 3.6.0 release

divijvaidya commented on code in PR #547: URL: https://github.com/apache/kafka-site/pull/547#discussion_r1330040052 ## blog.html: ## @@ -22,6 +22,46 @@ Blog + + + +Apache Kafka

Re: [VOTE] 3.6.0 RC0

Hey Satish Thank you for managing this release. I have a few comments: Documentation 1. Section: Zookeeper/Stable Version - The documentation states "The current stable branch is 3.5. Kafka is regularly updated to include the latest release in the 3.5 series." in the ZooKeeper section. That

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

See

Re: [VOTE] 3.6.0 RC0

Hey Satish, I have commented on KAFKA-15473. I think the changes in the PR look fine. I also feel this need not be a release blocker given there are other possibilities in which duplicates can manifest on the response of the end point in question (albeit we can potentially see more in number due

Re: [DISCUSS] KIP-975 Docker Image for Apache Kafka

Hi Ismael, I'm not trying to advocate against the docker image, I just pointed out that the current scoping of the KIP may be a bit too generic and thought that KIP-974 and KIP-975 were aiming for mostly the same thing and can be discussed under one umbrella. Apologies if this was rooted in a

[GitHub] [kafka-site] satishd opened a new pull request, #547: Added a blog entry for 3.6.0 release

satishd opened a new pull request, #547: URL: https://github.com/apache/kafka-site/pull/547 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [VOTE] 3.6.0 RC0

Hi Greg, Thanks for reporting the KafkaConnect issue. I replied to this issue on "Apache Kafka 3.6.0 release" email thread and on https://issues.apache.org/jira/browse/KAFKA-15473. I would like to hear other KafkaConnect experts' opinions on whether this issue is really a release blocker.

Re: [DISCUSS] KIP-892: Transactional Semantics for StateStores

Hi Bruno, Agreed, I can live with that for now. In an effort to keep the scope of this KIP from expanding, I'm leaning towards just providing a configurable default.state.isolation.level and removing IsolationLevel from the StateStoreContext. This would be compatible with adding support for

[jira] [Resolved] (KAFKA-15476) Improve checkstyle performance

[ https://issues.apache.org/jira/browse/KAFKA-15476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divij Vaidya resolved KAFKA-15476. -- Resolution: Fixed > Improve checkstyle performance > -- > >

[jira] [Created] (KAFKA-15476) Improve checkstyle performance

Divij Vaidya created KAFKA-15476: Summary: Improve checkstyle performance Key: KAFKA-15476 URL: https://issues.apache.org/jira/browse/KAFKA-15476 Project: Kafka Issue Type: Improvement

Re: Apache Kafka 3.6.0 release

Hi Greg, Is this API documented that it does not return duplicate entries? Can we also get an opinion from PMC/Committers who have KafkaConnect expertise on whether this issue is a release blocker? If we agree that it is not a release blocker then we can have a release note clarifying this

Re: [DISCUSS] KIP-892: Transactional Semantics for StateStores

Why do we need to add READ_COMMITTED to InMemoryKeyValueStore? I think it is perfectly valid to say InMemoryKeyValueStore do not support READ_COMMITTED for now, since READ_UNCOMMITTED is the de-facto default at the moment. Best, Bruno On 9/18/23 7:12 PM, Nick Telford wrote: Oh! One other

Re: Help to the community with review

Hi Taras, Thank you very much for your offers. Really appreciate it! For KIPs review, it's also great if the community can help review them if available. I'll also try my best to have a look when available. Thank you for your contribution! Luke On Tue, Sep 19, 2023 at 3:08 PM Taras Ledkov

Re:Help to the community with review

Hi, I'n not a committer to Kafka, but I offer my help with review of patches too. Please, tag me on GitHub (@tledkov). Unfortunately, no one offers help with KIPs review...

Re: Help to the community with review

Hi nizhikov, Thank you for your consideration and help! Yes, we really need the community developers to help review PRs to share the loading. One thing to note, PR review is also counted as one of the contribution! Please do that soon if you have spare cycle. :) BTW, I'll review your PRs this