Re: [DISCUSS] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Hi David, This KIP complements KIP-750 since it only proposes an additional change to the broker and tools modules. Ismael On Tue, Dec 26, 2023 at 1:38 PM David Arthur wrote: > Thanks, Ismael. I'm +1 on the proposal. > > Does this KIP essentially replace KIP-750? > > On Tue, Dec 26, 2023 at

Re: [DISCUSS] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Hi Divij, You asked and answered. :) Java 21 is too new and Apache Kafka would be requiring it before most other projects. Java 17, on the other hand, has been out for over 2 years and it is on its way to becoming the new baseline for many popular and related projects. Ismael On Tue, Dec 26,

Re: Kafka trunk test & build stability

I am still seeing quite a few OOM errors in the builds and I was curious if folks had any ideas on how to identify the cause and fix the issue. I was looking in gradle enterprise and found some info about memory usage, but nothing detailed enough to help figure the issue out. OOMs sometimes fail

[jira] [Resolved] (KAFKA-12679) Rebalancing a restoring or running task may cause directory livelocking with newly created task

[ https://issues.apache.org/jira/browse/KAFKA-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-12679. - Resolution: Fixed Marking this as done as per Lucas' comment that this is

Re: [DISCUSS] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Thanks, Ismael. I'm +1 on the proposal. Does this KIP essentially replace KIP-750? On Tue, Dec 26, 2023 at 3:57 PM Ismael Juma wrote: > Hi Colin, > > A couple of comments: > > 1. It is true that full support for OpenJDK 11 from Red Hat will end on > October 2024 (extended life support will

Re: [DISCUSS] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Thanks for starting this conversation Ismael. The proposal sounds great to me. I understand that JDK 21 is brand new and that may be the answer here, but I am curious to learn about your thoughts on moving the broker module directly to JDK 21 instead with 4.0, instead of JDK 17. (As a one-off

Re: Kafka trunk test & build stability

S2. We’ve looked into this before, and it wasn’t possible at the time with JUnit. We commonly set a timeout on each test class (especially integration tests). It is probably worth looking at this again and seeing if something has changed with JUnit (or our usage of it) that would allow a global

Re: [DISCUSS] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Hi Colin, A couple of comments: 1. It is true that full support for OpenJDK 11 from Red Hat will end on October 2024 (extended life support will continue beyond that), but Temurin claims to continue until 2027[1]. 2. If we set source/target/release to 11, then javac ensures compatibility with

Re: Kafka trunk test & build stability

Hey Stan & Sophie, About the 90-day view: That was restricted to only trunk builds. If we include PR builds, there's 100 builds > 5h20m in the last 90 days, which is a significant number. It may still be caused by environmental factors that S-3 would address, but we might be able to find a test

Re: [DISCUSS] Road to Kafka 4.0

Hi Divij, Thanks for the feedback. I agree that having a 3.8 release is beneficial but some of the comments in this message are inaccurate and could mislead the community and users. On Thu, Dec 21, 2023 at 7:00 AM Divij Vaidya wrote: > 1\ Durability/availability bugs in kraft - Even though

[jira] [Resolved] (KAFKA-15493) Ensure system tests work with Java 21

[ https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-15493. - Resolution: Fixed We can mark this as fixed. I ran the system tests with Java 21 and the

[jira] [Resolved] (KAFKA-15147) Measure pending and outstanding Remote Segment operations

[ https://issues.apache.org/jira/browse/KAFKA-15147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-15147. - Resolution: Fixed > Measure pending and outstanding Remote Segment operations >

[jira] [Resolved] (KAFKA-15327) Client consumer should commit offsets on close

[ https://issues.apache.org/jira/browse/KAFKA-15327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-15327. - Resolution: Fixed Resolving since this was merged   > Client consumer should

Re: Kafka trunk test & build stability

Regarding: S-4. Separate tests ran depending on what module is changed. > - This makes sense although is tricky to implement successfully, as > unrelated tests may expose problems in an unrelated change (e.g changing > core stuff like clients, the server, etc) Imo this avenue could provide a

Re: [DISCUSS] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Hi Ismael, Looks good to me. Looking forward to programming using features and types included in JDK17 in 4.0 and not having to program using a 10 year old programming language and library. Thanks! -- -José

[jira] [Resolved] (KAFKA-15780) Wait for consistent kraft metadata when creating topics in tests

[ https://issues.apache.org/jira/browse/KAFKA-15780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-15780. - Resolution: Fixed Resolving since this was merged. Nice work!   > Wait for

[jira] [Resolved] (KAFKA-15817) Avoid reconnecting to the same IP address if multiple addresses are available

[ https://issues.apache.org/jira/browse/KAFKA-15817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-15817. - Resolution: Fixed Resolving since this was merged. good job!   > Avoid

[jira] [Resolved] (KAFKA-16007) ZK migrations can be slow for large clusters

[ https://issues.apache.org/jira/browse/KAFKA-16007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-16007. - Resolution: Fixed Closing since it's merged   > ZK migrations can be slow for

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

See

Re: [DISCUSS] KIP-994: Minor Enhancements to ListTransactions and DescribeTransactions APIs

I have started a Vote on this KIP https://lists.apache.org/thread/yknx3bc4mk17bz2cpfr789lh8sx2lc39

[VOTE] KIP-994: Minor Enhancements to ListTransactions and DescribeTransactions APIs

I would like to start a Vote on KIP-994 https://cwiki.apache.org/confluence/display/KAFKA/KIP-994%3A+Minor+Enhancements+to+ListTransactions+and+DescribeTransactions+APIs

Re: [DISCUSS] KIP-994: Minor Enhancements to ListTransactions and DescribeTransactions APIs

Thanks Jun, Justine, Jason, Kirk, I have addressed your comments.

Re: [DISCUSS] Connect Jira component name

+1. I don't think we need a full vote for a change like this btw. :) Ismael On Tue, Dec 26, 2023, 9:04 AM Greg Harris wrote: > Hi Connect Developers, > > I noticed recently that we had two Jira components: "KafkaConnect" and > "connect", one with >1000 issues and one with 20 issues. I merged

Re: [DISCUSS] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Hi Ismael, +1 from me. Looking at the list of languages features for JDK17, from a developer productivity standpoint, the biggest wins are probably pattern matching and java.util.HexFormat. Also, Java 11 is getting long in the tooth, even though we never adopted it. It was released 6 years

[DISCUSS] Connect Jira component name

Hi Connect Developers, I noticed recently that we had two Jira components: "KafkaConnect" and "connect", one with >1000 issues and one with 20 issues. I merged the two tags, leaving the one labeled "KafkaConnect". "KafkaConnect" doesn't follow the standard naming convention set by all of the

[jira] [Created] (KAFKA-16051) Deadlock on connector initialization

Octavian Ciubotaru created KAFKA-16051: -- Summary: Deadlock on connector initialization Key: KAFKA-16051 URL: https://issues.apache.org/jira/browse/KAFKA-16051 Project: Kafka Issue Type:

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

See

Re: [PR] MINOR: Add Stanislav Kozlovski's GPG key [kafka-site]

satishd commented on PR #573: URL: https://github.com/apache/kafka-site/pull/573#issuecomment-1869611317 @stanislavkozlovski accepted and merged it to unblock you. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: [PR] MINOR: Add Stanislav Kozlovski's GPG key [kafka-site]

satishd merged PR #573: URL: https://github.com/apache/kafka-site/pull/573 -- 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:

Re: [PR] MINOR: Add Stanislav Kozlovski's GPG key [kafka-site]

stanislavkozlovski commented on PR #573: URL: https://github.com/apache/kafka-site/pull/573#issuecomment-1869582756 Ready for review 﫡 -- 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

Re: [PR] MINOR: Add Stanislav Kozlovski's GPG key [kafka-site]

stanislavkozlovski commented on PR #573: URL: https://github.com/apache/kafka-site/pull/573#issuecomment-1869572760 hm, this should probably use my apache email address. Converting this PR to draft until I do that -- This is an automated message from the Apache Git Service. To respond to

[PR] MINOR: Add Stanislav Kozlovski's GPG key [kafka-site]

stanislavkozlovski opened a new pull request, #573: URL: https://github.com/apache/kafka-site/pull/573 This patch adds Stanislav Kozlovski's newly-generated GPG key to the website's public keys. I ran: ``` gpg --list-sigs Stanislav Kozlovski >> KEYS && gpg --armor --export

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.7 #35

See Changes: -- [...truncated 2998 lines...] Note: Recompile with -Xlint:deprecation for details. Note:

Re: Kafka trunk test & build stability

Great discussion! Greg, that was a good call out regarding the two long-running builds. I missed that 90d view. My takeaway from that is that our average build time for tests is between 3-4 hours. Which in of itself seems large. But then reconciling this with Sophie's statement - is it

[jira] [Created] (KAFKA-16050) consumer was removed from group，but still can poll data from kafka, data duplicate

Xin created KAFKA-16050: --- Summary: consumer was removed from group，but still can poll data from kafka, data duplicate Key: KAFKA-16050 URL: https://issues.apache.org/jira/browse/KAFKA-16050 Project: Kafka

[jira] [Resolved] (KAFKA-15818) Implement max poll interval

[ https://issues.apache.org/jira/browse/KAFKA-15818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-15818. - Resolution: Fixed > Implement max poll interval > --- >

[jira] [Resolved] (KAFKA-16026) AsyncConsumer does not send a poll event to the background thread

[ https://issues.apache.org/jira/browse/KAFKA-16026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-16026. - Resolution: Fixed https://github.com/apache/kafka/pull/15035   >

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

Hey all, As the release manager for 3.7.0, I am pretty interested to know if we should consider this a blocker. Do we have clarity as to whether users could practically rely on this Go script? From a shallow look, it's only used in one line in the Dockerfile. I guess the downside is that images