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

See

Re: [DISCUSS] Apache Kafka 3.6.2 release

Hi team, We should focus on regressions and cve fixes for releases like this one (second bug fix and it's not the most recently released version). The idea is to reduce the risk of regressions since it may well be the last official release on this branch. Ismael On Thu, Mar 14, 2024, 1:39 AM

[jira] [Created] (KAFKA-16378) Under tiered storage, deleting local logs does not free disk space

Jianbin Chen created KAFKA-16378: Summary: Under tiered storage, deleting local logs does not free disk space Key: KAFKA-16378 URL: https://issues.apache.org/jira/browse/KAFKA-16378 Project: Kafka

Re: [DISCUSS] KIP-1020: Deprecate `window.size.ms` in `StreamsConfig`

> > Should we change it do `.serializer` and `.deserialize`? That's a good point -- if we're going to split this up by defining the config in both the TimeWindowedSerializer and TimeWindowedDeserializer, then it makes perfect sense to go a step further and actually define only the relevant

Re: [DISCUSS] KIP-1027 Add MockFixedKeyProcessorContext

Thanks for the feedback Matthias! The reason I proposed the extension of MockProcessorContext was more to do with the internals of the class (MockRecordMetadata, CapturedPunctuator and CapturedForward). However, I do see your point, I would then think to split MockProcessorContext and

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

See

Re: [DISCUSS] KIP-1020: Deprecate `window.size.ms` in `StreamsConfig`

By "don't add them" do you just mean we would not have any actual variables defined anywhere for these configs (eg WINDOW_SIZE_MS) and simply document -- somewhere -- that one can use the string "window.size.ms" when configuring a command-line client with a windowed serde? Yes. That's the

Re: [DISCUSS] KIP-853: KRaft Controller Membership Changes

Hi, Jose, Thanks for the reply. A few more comments. 37. Have you updated the wiki? It seems that LeaderIdAndEpoch and NodeEpoint are still two separate structs. 45. kafka-storage format --cluster-id --release-version 3.8 --standalone --config controller.properties It seems that

[jira] [Resolved] (KAFKA-14971) Flaky Test org.apache.kafka.connect.mirror.integration.IdentityReplicationIntegrationTest#testSyncTopicConfigs

[ https://issues.apache.org/jira/browse/KAFKA-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-14971. Resolution: Duplicate KAFKA-15945 has filed PR so close this ticket > Flaky Test >

[jira] [Resolved] (KAFKA-15523) Flaky test org.apache.kafka.connect.mirror.integration.MirrorConnectorsIntegrationSSLTest.testSyncTopicConfigs

[ https://issues.apache.org/jira/browse/KAFKA-15523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-15523. Resolution: Duplicate KAFKA-15945 has filed PR so close this ticket > Flaky test >

[jira] [Created] (KAFKA-16377) Fix flaky HighAvailabilityTaskAssignorIntegrationTest.shouldScaleOutWithWarmupTasksAndPersistentStores

Chia-Ping Tsai created KAFKA-16377: -- Summary: Fix flaky HighAvailabilityTaskAssignorIntegrationTest.shouldScaleOutWithWarmupTasksAndPersistentStores Key: KAFKA-16377 URL:

[jira] [Created] (KAFKA-16376) Fix flaky ReplicaManagerTest.testRemoteFetchExpiresPerSecMetric

Chia-Ping Tsai created KAFKA-16376: -- Summary: Fix flaky ReplicaManagerTest.testRemoteFetchExpiresPerSecMetric Key: KAFKA-16376 URL: https://issues.apache.org/jira/browse/KAFKA-16376 Project: Kafka

[jira] [Reopened] (KAFKA-15691) Add new system tests to use new consumer

[ https://issues.apache.org/jira/browse/KAFKA-15691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True reopened KAFKA-15691: --- > Add new system tests to use new consumer > > >

Re: [DISCUSS] KIP-1026: Handling producer snapshot when upgrading from < v2.8.0 for Tiered Storage

Hi Arpit, Thanks for the clarification. Replying here without updating the KIP is fine for now. I disagree with your evaluation of the backwards compatibility. If you change the return type of a method, that breaks both source and binary compatibility. After upgrading, plugin implementations

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

Hi Omnia, Thanks for the KIP. I don't think we can adapt the ForwardingAdmin as-is for use as a first-class Connect plugin. 1. It doesn't have a default constructor, and so can't be included in the existing plugin discovery mechanisms. 2. It doesn't implement Versioned, and so won't have version

[jira] [Created] (KAFKA-16375) Fix logic for discarding reconciliation if member rejoined

Lianet Magrans created KAFKA-16375: -- Summary: Fix logic for discarding reconciliation if member rejoined Key: KAFKA-16375 URL: https://issues.apache.org/jira/browse/KAFKA-16375 Project: Kafka

Re: [DISCUSS] Personal branches under apache/kafka

+1 to delete personal branches Also +1 to Matthias to disable push if the branch is nonexistent > committers for various > reasons, bugfix, tests. That is interesting. Can anyone share the details here? I’d like to know the bug/test which need to have a branch. Chia-Ping > Mickael Maison

Re: [DISCUSS] Personal branches under apache/kafka

An alternative would be to have a convention for personal branches. For example "tmp/ijuma/blah". I don't have a strong opinion, but it seems useful if people want to collaborate on a branch. Ismael On Wed, Mar 13, 2024 at 11:02 AM Mickael Maison wrote: > Hi, > > We have accumulated a number

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

Hi Omnia, +1 (binding), thanks for the KIP Mickael On Tue, Mar 5, 2024 at 10:46 AM Omnia Ibrahim wrote: > > Hi everyone, I would like to start the vote on KIP-981: Manage Connect topics > with custom implementation of Admin >

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.7 #109

See

Re: [DISCUSS] Personal branches under apache/kafka

+1 Sounds like a good idea to me. -Bill On Wed, Mar 13, 2024 at 2:55 PM Matthias J. Sax wrote: > +1 > > Should be fine to just delete all of them (as long as nobody raised > objections). > > Not sure if we could enable some protection GitHub side that disallow to > push into non-existing

[PR] Adding OREXES to powered-by section [kafka-site]

siifuu opened a new pull request, #591: URL: https://github.com/apache/kafka-site/pull/591 OREXES is an it-security consultancy providing customers with specialized solutions suited to their use cases. They service large customers in the public and private sector in Germany. -- This

Re: [DISCUSS] KIP-1026: Handling producer snapshot when upgrading from < v2.8.0 for Tiered Storage

Hi Greg, I do not have access to update the KIP , Divij is helping me to do it. Meanwhile let me update your queries here. Backward compatibility: These changes will not impact the existing functionality as the existing behaviour always expects producer snapshot files to be present for a given

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

See

[jira] [Resolved] (KAFKA-16180) Full metadata request sometimes fails during zk migration

[ https://issues.apache.org/jira/browse/KAFKA-16180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur resolved KAFKA-16180. -- Resolution: Fixed > Full metadata request sometimes fails during zk migration >

[jira] [Resolved] (KAFKA-16226) Java client: Performance regression in Trogdor benchmark with high partition counts

[ https://issues.apache.org/jira/browse/KAFKA-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-16226. - Resolution: Fixed > Java client: Performance regression in Trogdor benchmark with high

Re: [DISCUSS] Apache Kafka 3.6.2 release

Hi Edoardo, Sure, we can include KAFKA-16369 based PR reviews. Thanks, On Thu, Mar 14, 2024 at 3:16 PM Edoardo Comar wrote: > Hi Manikumar, > can we please include > https://issues.apache.org/jira/browse/KAFKA-16369 > in 3.6.2 ? > While it's

Re: [DISCUSS] Apache Kafka 3.6.2 release

Hi Divij, 1. I will take a look 2. I am not sure what we did for earlier releases. But we can update the dependencies if any CVE exists 3. Thanks for looking into backports. 4. Sure, we can ping the committers where PR is available 5. I have not looked at 3.7 bugs. I will also take a look.

[jira] [Created] (KAFKA-16374) High watermark updates should have a higher priority

David Jacot created KAFKA-16374: --- Summary: High watermark updates should have a higher priority Key: KAFKA-16374 URL: https://issues.apache.org/jira/browse/KAFKA-16374 Project: Kafka Issue

[jira] [Created] (KAFKA-16373) Docker Official Image for Apache Kafka

Krish Vora created KAFKA-16373: -- Summary: Docker Official Image for Apache Kafka Key: KAFKA-16373 URL: https://issues.apache.org/jira/browse/KAFKA-16373 Project: Kafka Issue Type: New Feature

Re: [DISCUSS] Minimum constraint for segment.ms

Hi, Divij. This isn't about config default value/constraint change though, I found there's a behavior discrepancy in max.block.ms config, which may cause breaking change if we change the behavior. The detail is described in the ticket: https://issues.apache.org/jira/browse/KAFKA-16372 What do

[jira] [Created] (KAFKA-16372) max.block.ms behavior inconsistency with javadoc and the config description

Haruki Okada created KAFKA-16372: Summary: max.block.ms behavior inconsistency with javadoc and the config description Key: KAFKA-16372 URL: https://issues.apache.org/jira/browse/KAFKA-16372 Project:

[DISCUSS] KIP-1031: Control offset translation in MirrorSourceConnector

Hi everyone, I would like to start a discussion thread for KIP-1031: Control offset translation in MirrorSourceConnector https://cwiki.apache.org/confluence/display/KAFKA/KIP-1031%3A+Control+offset+translation+in+MirrorSourceConnector Thanks Omnia

[jira] [Created] (KAFKA-16371) Unstable committed offsets after triggering commits where some metadata for some partitions are over the limit

mlowicki created KAFKA-16371: Summary: Unstable committed offsets after triggering commits where some metadata for some partitions are over the limit Key: KAFKA-16371 URL:

Re: [DISCUSS] Apache Kafka 3.6.2 release

Hi Manikumar, can we please include https://issues.apache.org/jira/browse/KAFKA-16369 in 3.6.2 ? While it's an issue still in trunk we actually discovered it our 3.6.1 systems thanks, Edo On Thu, 14 Mar 2024 at 08:39, Divij Vaidya wrote: > > Hi Manikumar, > > 1. Can you please take a look at

[jira] [Created] (KAFKA-16370) offline rollback procedure from kraft mode to zookeeper mode.

kaushik srinivas created KAFKA-16370: Summary: offline rollback procedure from kraft mode to zookeeper mode. Key: KAFKA-16370 URL: https://issues.apache.org/jira/browse/KAFKA-16370 Project: Kafka

Re: [DISCUSS] Apache Kafka 3.6.2 release

Hi Manikumar, 1. Can you please take a look at https://github.com/apache/kafka/pull/15490 which is a bug fix specific to the 3.6.x branch? 2. Should we do a one-time update of all dependencies in 3.6.x branch before releasing 3.6.2? 3. We fixed quite a lot of flaky tests in 3.7.x. I will see if

[jira] [Resolved] (KAFKA-15997) Ensure fairness in the uniform assignor

[ https://issues.apache.org/jira/browse/KAFKA-15997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-15997. - Resolution: Fixed This issue got resolved by https://issues.apache.org/jira/browse/KAFKA-16249.

[jira] [Resolved] (KAFKA-16249) Improve reconciliation state machine

[ https://issues.apache.org/jira/browse/KAFKA-16249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-16249. - Fix Version/s: 3.8.0 Resolution: Fixed > Improve reconciliation state machine >

Re: [DISCUSS] Apache Kafka 3.6.2 release

Hi all, Here is the release plan for 3.6.2: https://cwiki.apache.org/confluence/display/KAFKA/Release+plan+3.6.2 Currently there is one open non-blocker issue. I plan to generate the first release candidate once the issue is resolved and no other issues are raised in the meantime. Thanks,

Re: [DISCUSS] KIP-950: Tiered Storage Disablement

Hi Christo, Any update with this KIP? If you don't have time to complete it, I can collaborate with you to work on it. Thanks. Luke On Wed, Jan 17, 2024 at 11:38 PM Satish Duggana wrote: > Hi Christo, > Thanks for volunteering to contribute to the KIP discussion. I suggest > considering this

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.6 #152

See Changes: -- [...truncated 377525 lines...] [2024-03-14T06:09:03.004Z] Gradle Test Run :connect:runtime:test > Gradle Test Executor 48 >

Re: [VOTE] KIP-956: Tiered Storage Quotas

Thanks for the KIP! +1 from me. Luke On Sun, Mar 10, 2024 at 8:44 AM Satish Duggana wrote: > Thanks Abhijeet for the KIP, +1 from me. > > > On Sat, 9 Mar 2024 at 1:51 AM, Kamal Chandraprakash < > kamal.chandraprak...@gmail.com> wrote: > > > +1 (non-binding), Thanks for the KIP, Abhijeet! > > >