[jira] [Created] (KAFKA-15576) Add 3.2.0 to broker/client and streams upgrade/compatibility tests

Satish Duggana created KAFKA-15576: -- Summary: Add 3.2.0 to broker/client and streams upgrade/compatibility tests Key: KAFKA-15576 URL: https://issues.apache.org/jira/browse/KAFKA-15576 Project:

[ANNOUNCE] Apache Kafka 3.6.0

The Apache Kafka community is pleased to announce the release for Apache Kafka 3.6.0 This is a minor release and it includes fixes and improvements from 238 JIRAs. All of the changes in this release can be found in the release notes: https://www.apache.org/dist/kafka/3.6.0/RELEASE_NOTES.html An

[jira] [Resolved] (KAFKA-15535) Add documentation of "remote.log.index.file.cache.total.size.bytes" configuration property.

[ https://issues.apache.org/jira/browse/KAFKA-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana resolved KAFKA-15535. Resolution: Fixed > Add documentation of "remote.log.index.file.cache.total.size.bytes"

[jira] [Resolved] (KAFKA-15507) adminClient should not throw retriable exception when closing instance

[ https://issues.apache.org/jira/browse/KAFKA-15507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-15507. --- Fix Version/s: 3.7.0 Resolution: Fixed > adminClient should not throw retriable exception

Re: [PR] Added a blog entry for 3.6.0 release [kafka-site]

satishd merged PR #547: URL: https://github.com/apache/kafka-site/pull/547 -- 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] Added a blog entry for 3.6.0 release [kafka-site]

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

Re: [PR] MINOR Update default docs point to 3.6.0 release docs [kafka-site]

satishd merged PR #556: URL: https://github.com/apache/kafka-site/pull/556 -- 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 Update default docs point to 3.6.0 release docs [kafka-site]

satishd commented on code in PR #556: URL: https://github.com/apache/kafka-site/pull/556#discussion_r1353943855 ## downloads.html: ## @@ -6,12 +6,41 @@ Download -3.5.1 is the latest release. The current stable version is 3.5.1 +3.6.0 is the latest

Re: [PR] MINOR Updated 3.6 javadocs by replacing 3.6.0-SNAPSHOT with 3.6.0 [kafka-site]

satishd merged PR #557: URL: https://github.com/apache/kafka-site/pull/557 -- 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: [DISCUSS] KIP-966: Eligible Leader Replicas

Hi, Calvin, One more comment. "The first partition to fetch details for. -1 means to fetch all partitions." It seems that FirstPartitionId of 0 naturally means fetching all partitions? Thanks, Jun On Tue, Oct 10, 2023 at 12:40 PM Calvin Liu wrote: > Hi Jun, > Yeah, with the current Metadata

Re: [DISCUSS] KIP-714: Client metrics and observability

Andrew, yes I would like to get this change into KIP-714 right way. Seems to be important, as we don't know if/when a follow-up KIP for Kafka Streams would land. I was also thinking (and discussed with a few others) how to expose it, and we would propose the following: We add a new method

[jira] [Created] (KAFKA-15575) Prevent Connectors from exceeding tasks.max configuration

Greg Harris created KAFKA-15575: --- Summary: Prevent Connectors from exceeding tasks.max configuration Key: KAFKA-15575 URL: https://issues.apache.org/jira/browse/KAFKA-15575 Project: Kafka

Re: KAFKA-15571 Review

Hi Bruno, Thanks for taking a look. I’ve added a test as well. Is it fair to say that we can expect 3.5.2 release with this fix? I can cherry pick the changes into the 3.5 branch. Best, Levani > On 10. Oct 2023, at 16:35, Bruno Cadonna wrote: > > Hi Levani, > > I think you found a bug and

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

Hi Jun, Yeah, with the current Metadata request handling, we only return errors on the Topic level, like topic not found. It seems that querying a specific partition is not a valid use case. Will update. Thanks On Tue, Oct 10, 2023 at 11:55 AM Jun Rao wrote: > Hi, Calvin, > > 60. If the range

Re: [DISCUSS] KIP-969: Support range interactive queries for versioned state stores

Thanks, Matthias and Bruno, for the feedback on KIP-969. Here is a summary of the updates I made to the KIP: 1. I liked the idea of renaming methods as Matthias suggested. 2. I removed the allversions() method as I did in KIP-968. To retrieve the latest value(s), the user must call just

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

Hi, Calvin, 60. If the range query has errors for some of the partitions, do we expect different responses when querying particular partitions? Thanks, Jun On Tue, Oct 10, 2023 at 10:50 AM Calvin Liu wrote: > Hi Jun > 60. Yes, it is a good question. I was thinking the API could be flexible

Re: [DISCUSS] KIP-987: Connect Static Assignments

Hi Mickael, I'm not Chris but I hope I can still respond to your questions :) 1a. This system behaves best when connectors and tasks are known in advance, but I don't think that is a requirement. I clarified that the worker configurations are permissive of non-existent jobs, which allows for

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

Hi Jun 60. Yes, it is a good question. I was thinking the API could be flexible to query the particular partitions if the range query has errors for some of the partitions. Not sure whether it is a valid assumption, what do you think? 61. Good point, I will update them to partition level with the

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

Hi, Calvin, A few more minor comments on your latest update. 60. DescribeTopicRequest: When will the Partitions field be used? It seems that the FirstPartitionId field is enough for AdminClient usage. 61. Could we make the limit for DescribeTopicRequest, ElectLeadersRequest, GetReplicaLogInfo

Re: [DISCUSS] KIP-987: Connect Static Assignments

Hey Tom, Thanks for your comments! I appreciate your insight here and on the Strimzi proposal. 1. Fixed, thanks. 2. We haven't removed a protocol yet, so workers still announce that they can use the old protocol versions, and the group coordinator will choose the highest mutually supported

Re: [PR] MINOR Updated 3.6 javadocs by replacing 3.6.0-SNAPSHOT with 3.6.0 [kafka-site]

satishd commented on PR #557: URL: https://github.com/apache/kafka-site/pull/557#issuecomment-1755872023 >@satishd how were these files produced? It seems like the contents of the 36/javadoc directory in this PR differ from the ones for the release candidate in

[jira] [Created] (KAFKA-15574) Integrate partition assignment reconciliation with heartbeat request manager

Kirk True created KAFKA-15574: - Summary: Integrate partition assignment reconciliation with heartbeat request manager Key: KAFKA-15574 URL: https://issues.apache.org/jira/browse/KAFKA-15574 Project:

[jira] [Created] (KAFKA-15573) Implement auto-commit on partition assignment revocation

Kirk True created KAFKA-15573: - Summary: Implement auto-commit on partition assignment revocation Key: KAFKA-15573 URL: https://issues.apache.org/jira/browse/KAFKA-15573 Project: Kafka Issue

Re: [DISCUSS] KIP-968: Support single-key_multi-timestamp interactive queries (IQv2) for versioned state stores

Thank you all for the very exact and constructive comments. I really enjoyed reading your ideas and all the important points you made me aware of. I updated KIP-968 as follows: 1. If the key or time bounds are null, the method returns NPE. 2. The "valid" word: I removed the sentence "all

Re: [DISCUSS] KIP-987: Connect Static Assignments

Hi Chris, Thanks for the KIP! 1) With this mechanism it seems Connect administrators have to know in advanced the names of connectors that will be running. As far as I can tell, static.connectors and static.tasks will require restarting the worker to change. Also you don't specify if these

[jira] [Created] (KAFKA-15572) Race condition between future log dir roll and replace current with future log during alterReplicaLogDirs

Lucian Ilie created KAFKA-15572: --- Summary: Race condition between future log dir roll and replace current with future log during alterReplicaLogDirs Key: KAFKA-15572 URL:

Re: [PR] MINOR Updated 3.6 javadocs by replacing 3.6.0-SNAPSHOT with 3.6.0 [kafka-site]

C0urante commented on PR #557: URL: https://github.com/apache/kafka-site/pull/557#issuecomment-1755453319 @satishd how were these files produced? It seems like the contents of the `36/javadoc` directory in this PR differ from the ones for the release candidate in

Re: KAFKA-15571 Review

Hi Levani, I think you found a bug and you are looking at the right place! I commented on the PR. Best, Bruno On 10/10/23 3:02 PM, Levani Kokhreidze wrote: Hello, We’ve been looking at a https://issues.apache.org/jira/browse/KAFKA-10575 but seems implementation has a bug and user defined

KAFKA-15571 Review

Hello, We’ve been looking at a https://issues.apache.org/jira/browse/KAFKA-10575 but seems implementation has a bug and user defined `StateRestoreListener#onRestoreSuspended` is not called because DelegatingStateRestoreListener was not updated. Here’s the PR that fixes it:

[jira] [Created] (KAFKA-15571) StateRestoreListener#onRestoreSuspended is never called because wrapper DelegatingStateRestoreListener doesn't implement onRestoreSuspended

Levani Kokhreidze created KAFKA-15571: - Summary: StateRestoreListener#onRestoreSuspended is never called because wrapper DelegatingStateRestoreListener doesn't implement onRestoreSuspended Key: KAFKA-15571

Re: Re: Re: [DISCUSS] KIP-972: Add the metric of the current running version of kafka

Hi Hudeqi, Rather than creating a gauge with a dummy value, could we add the version (and commitId) as tags to an existing metric. For example, the alongside the existing Version and CommitId metrics we have StartTimeMs. Maybe we can have a StartTimeMs metrics with the version and commitId) as

[DISCUSS] KIP-975 Docker Image for Apache Kafka

Hey folks! Please feel free to ask any additional questions concerning this KIP. If there are no additional queries, shall we consider moving forward with the voting process? Thanks and regards, Vedarth

[jira] [Created] (KAFKA-15570) Add unit tests for MemoryConfigBackingStore

Yash Mayya created KAFKA-15570: -- Summary: Add unit tests for MemoryConfigBackingStore Key: KAFKA-15570 URL: https://issues.apache.org/jira/browse/KAFKA-15570 Project: Kafka Issue Type: Test

Re: [PR] MINOR Updated 3.6 javadocs by replacing 3.6.0-SNAPSHOT with 3.6.0 [kafka-site]

satishd commented on PR #557: URL: https://github.com/apache/kafka-site/pull/557#issuecomment-1754991366 cc @C0urante -- 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

Re: [PR] Added 3.6 documentation [kafka-site]

satishd commented on PR #541: URL: https://github.com/apache/kafka-site/pull/541#issuecomment-1754988854 >@satishd the version in the Javadocs here is 3.6.0-SNAPSHOT. Do you plan to address this before announcing the 3.6.0 release? Right @C0urante. I plan to have the release

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

See Changes: -- [...truncated 316154 lines...] [INFO] Parameter: version, Value: 0.1 [INFO] Parameter: groupId, Value: streams.examples [INFO] Parameter: artifactId,

[jira] [Resolved] (KAFKA-15385) Replace EasyMock with Mockito for AbstractStreamTest

[ https://issues.apache.org/jira/browse/KAFKA-15385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christo Lolov resolved KAFKA-15385. --- Resolution: Duplicate Closing this in favour of

[jira] [Resolved] (KAFKA-15382) Replace EasyMock with Mockito for KStreamTransformValuesTest

[ https://issues.apache.org/jira/browse/KAFKA-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christo Lolov resolved KAFKA-15382. --- Resolution: Duplicate Closing this ticket in favour of

[jira] [Resolved] (KAFKA-15383) Replace EasyMock with Mockito for KTableImplTest

[ https://issues.apache.org/jira/browse/KAFKA-15383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christo Lolov resolved KAFKA-15383. --- Resolution: Duplicate Closing this ticket in favour of

[jira] [Resolved] (KAFKA-15384) Replace EasyMock with Mockito for KTableTransformValuesTest

[ https://issues.apache.org/jira/browse/KAFKA-15384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christo Lolov resolved KAFKA-15384. --- Resolution: Fixed Closing this ticket in favour of

[jira] [Resolved] (KAFKA-14927) Dynamic configs not validated when using kafka-configs and --add-config-file

[ https://issues.apache.org/jira/browse/KAFKA-14927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-14927. --- Fix Version/s: 3.7.0 Assignee: Aman Singh (was: José Armando García Sancio)

Re: Apache Kafka 3.7.0 Release

Thanks Stan! +1 Best, Bruno On 10/10/23 7:24 AM, Luke Chen wrote: Thanks Stanislav! On Tue, Oct 10, 2023 at 3:05 AM Josep Prat wrote: Thanks Stanislav! ——— Josep Prat Aiven Deutschland GmbH Alexanderufer 3-7, 10117 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer:

Re: [DISCUSS] KIP-987: Connect Static Assignments

Hi Greg, Many thanks for the KIP. Here are a few initial questions 1. Incomplete sentence: "But Connect is not situated to be able to manage resources directly, as workers are given a fixed " 2. You explain how sessioned is now a subset of static, but what happens in a cluster where some workers