[jira] [Created] (KAFKA-15472) Kraft broker does not seem to support sasl/scram authentication

RivenSun created KAFKA-15472: Summary: Kraft broker does not seem to support sasl/scram authentication Key: KAFKA-15472 URL: https://issues.apache.org/jira/browse/KAFKA-15472 Project: Kafka Issu

[jira] [Resolved] (KAFKA-15472) Kraft broker does not seem to support sasl/scram authentication

[ https://issues.apache.org/jira/browse/KAFKA-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RivenSun resolved KAFKA-15472. -- Fix Version/s: 3.5.0 Resolution: Fixed > Kraft broker does not seem to support sasl/scram authe

[GitHub] [kafka-site] satishd merged pull request #544: Fixed a few links in documentation.html

satishd merged PR #544: URL: https://github.com/apache/kafka-site/pull/544 -- 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, e-mail: dev-unsubscr...@kafka.apache.

[jira] [Resolved] (KAFKA-13973) block-cache-capacity metrics worth twice as much as normal

[ https://issues.apache.org/jira/browse/KAFKA-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-13973. --- Resolution: Fixed > block-cache-capacity metrics worth twice as much as normal > ---

Re:[DISCUSS] KIP-967: Support custom SSL configuration for Kafka Connect RestServer

Hi Kafka Team. Looks like the code freeze of 3.6.0 release done. I hope that community members have more time for review. Please pay your attention for the KIP-967: Support custom SSL configuration for Kafka Connect RestServer [1]. The purpose of this KIP is add ability to use custom SSL factory

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

See

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

See

RE: [VOTE] KIP-942: Add Power(ppc64le) support

Thanks for the votes everyone. Closing this voting for KIP and moving it to adopted section. -Original Message- From: Colin McCabe Sent: Friday, September 15, 2023 9:55 AM To: dev@kafka.apache.org Subject: [EXTERNAL] Re: [VOTE] KIP-942: Add Power(ppc64le) support It looks like the KIP

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

See

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

Hi Nick, since I last read it in April, the KIP has become much cleaner and easier to read. Great work! It feels to me the last big open point is whether we can implement isolation level as a query parameter. I understand that there are implementation concerns, but as Colt says, it would be a gre

Re: [VOTE] 3.6.0 RC0

Hey Satish, thanks for getting the RC underway! I noticed that the PR for the 3.6 blog post is merged. This makes the blog post live on the Kafka website https://kafka.apache.org/blog.html. The blog post (along with other public announcements) is usually the last thing we do as part of the release

[GitHub] [kafka-site] mumrah commented on pull request #542: Added a blog entry for 3.6.0 release

mumrah commented on PR #542: URL: https://github.com/apache/kafka-site/pull/542#issuecomment-1723818513 @satishd @showuon I think we need to revert this change until the 3.6 release is complete. Here's what I just sent out on the mailing list RC0 thread: > I noticed that the PR for th

[GitHub] [kafka-site] jlprat opened a new pull request, #546: Revert "Added a blog entry for 3.6.0 release"

jlprat opened a new pull request, #546: URL: https://github.com/apache/kafka-site/pull/546 Reverts apache/kafka-site#542 This way the blog post is not visible to visitors yet. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [kafka-site] jlprat commented on pull request #546: Revert "Added a blog entry for 3.6.0 release"

jlprat commented on PR #546: URL: https://github.com/apache/kafka-site/pull/546#issuecomment-1723836979 @satishd @mumrah and @showuon Feel free to merge this one to "unpublish the blog post" -- This is an automated message from the Apache Git Service. To respond to the message, please log

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

Hi everyone, I agree that having IsolationLevel be determined at query-time is the ideal design, but there are a few sticking points: 1. There needs to be some way to communicate the IsolationLevel down to the RocksDBStore itself, so that the query can respect it. Since stores are "layered" in fu

[GitHub] [kafka-site] jlprat merged pull request #546: Revert "Added a blog entry for 3.6.0 release"

jlprat merged PR #546: URL: https://github.com/apache/kafka-site/pull/546 -- 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, e-mail: dev-unsubscr...@kafka.apache.o

[GitHub] [kafka-site] jlprat commented on pull request #542: Added a blog entry for 3.6.0 release

jlprat commented on PR #542: URL: https://github.com/apache/kafka-site/pull/542#issuecomment-1723923384 I just reverted it and merged it. @satishd feel free to "reopen" this one again. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

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

Oh! One other concern I haven't mentioned: if we make IsolationLevel a query-time constraint, then we need to add support for READ_COMMITTED to InMemoryKeyValueStore too, which will require some changes to the implementation. On Mon, 18 Sept 2023 at 17:24, Nick Telford wrote: > Hi everyone, > >

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

See

Help to the community with review

Hello. From my experience it’s hard to get Kafka patches reviewed in timely manner. I think that the reason is committers has different priorities and lack of free time. So I offer my help with review of patches if anyone from community are need it. Please, tag me on GitHub (@nizhikov) if you h

Re: [VOTE] 3.6.0 RC0

Hi Satish, Thanks for running the release. 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

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

satishd commented on PR #542: URL: https://github.com/apache/kafka-site/pull/542#issuecomment-1724140456 Thanks @mumrah for clarifying the merge timeline for the blog section. I will open a PR and wait for the release candidate to be finalized before merging it. I will also update the w

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

Greg Harris created KAFKA-15473: --- Summary: Connect connector-plugins endpoint shows duplicate plugins Key: KAFKA-15473 URL: https://issues.apache.org/jira/browse/KAFKA-15473 Project: Kafka Issu

Re: Apache Kafka 3.6.0 release

Hi Satish, While validating 3.6.0-rc0, I noticed this regression as compared to 3.5.1: https://issues.apache.org/jira/browse/KAFKA-15473 Impact: The `connector-plugins` endpoint lists duplicates which may cause confusion for users, or poor behavior in clients. Using the other REST API endpoints a

Re: [VOTE] 3.6.0 RC0

Hey all, I noticed this regression in RC0: https://issues.apache.org/jira/browse/KAFKA-15473 I've mentioned it in the release thread, and I'm working on a fix. I'm -1 (non-binding) until we determine if this regression is a blocker. Thanks! On Mon, Sep 18, 2023 at 10:56 AM Josep Prat wrote: >

[jira] [Resolved] (KAFKA-15306) Integrate committed offsets logic when updating fetching positions

[ https://issues.apache.org/jira/browse/KAFKA-15306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-15306. - Fix Version/s: 3.7.0 Resolution: Fixed merged the PR to trunk > Integrate committed offsets logi

[jira] [Created] (KAFKA-15474) AbstractCoordinator.testWakeupAfterSyncGroupReceivedExternalCompletion seems flaky

Philip Nee created KAFKA-15474: -- Summary: AbstractCoordinator.testWakeupAfterSyncGroupReceivedExternalCompletion seems flaky Key: KAFKA-15474 URL: https://issues.apache.org/jira/browse/KAFKA-15474 Proje

[jira] [Created] (KAFKA-15475) Timeout request might retry forever even if the user API times out in AsyncConsumer

Philip Nee created KAFKA-15475: -- Summary: Timeout request might retry forever even if the user API times out in AsyncConsumer Key: KAFKA-15475 URL: https://issues.apache.org/jira/browse/KAFKA-15475 Proje

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

See

Re: Apache Kafka 3.6.0 release

Hey Satish, After investigating further, I believe that this is a regression, but mostly a cosmetic one. I don't think there is significant risk of breaking clients with this change, but it would be confusing for users, so I'd still like to get the fix into the next RC. I've opened a PR here: http

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

See

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

Hi Colin, For the unclean.recovery.strategy config name, how about we use the following None. It basically means no unclean recovery will be performed. Aggressive. It means availability goes first. Whenever the partition can't elect a durable replica, the controller will try the unclean recovery. B

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

Hi Colin, Also, can we deprecate unclean.leader.election.enable in 4.0? Before that, we can have both the config unclean.recovery.strategy and unclean.leader.election.enable and using the unclean.recovery.Enabled to determine which config to use during the unclean leader election. On Mon, Sep 18,

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 wee