[jira] [Created] (KAFKA-14465) java.lang.NumberFormatException: For input string: "index"

jianbin.chen created KAFKA-14465: Summary: java.lang.NumberFormatException: For input string: "index" Key: KAFKA-14465 URL: https://issues.apache.org/jira/browse/KAFKA-14465 Project: Kafka

Re: [DISCUSS] KIP-890 Server Side Defense

Thanks for the background. 20/30: SGTM. My proposal was only focusing to avoid dangling transactions if records are added without registered partition. -- Maybe you can add a few more details to the KIP about this scenario for better documentation purpose? 40: I think you hit a fair point

Re: [DISCUSS] KIP-889 Versioned State Stores

Thanks Victoria. I did not re-read the KIP in full on the wiki but only your email. Points (1)-(8) SGTM. About (9): I slightly prefer to add `VersionedRecord` interface (also like the name). I agree that it's low overhead and providing a clean path forward for future changes seems worth it

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

See

[jira] [Resolved] (KAFKA-14271) Topic recreation fails in KRaft mode when topic contains collidable characters

[ https://issues.apache.org/jira/browse/KAFKA-14271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Tolar resolved KAFKA-14271. --- Fix Version/s: 3.4.0 3.3.2 Resolution: Duplicate Haven't tested

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.3 #135

See Changes: -- [...truncated 487211 lines...] [2022-12-12T22:58:20.214Z] [2022-12-12T22:58:20.214Z] org.apache.kafka.streams.integration.StandbyTaskCreationIntegrationTest

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

See

Re: [DISCUSS] Apache Kafka 3.3.2

Hi Ron, You're in luck, I was just about to start generating a release candidate! I'm fine with including the fix for KAFKA-14392 in 3.3.2. Cheers, Chris On Mon, Dec 12, 2022 at 3:13 PM Ron Dagostino wrote: > Hi Chris. >

Re: [DISCUSS] Apache Kafka 3.4.0 release

Hi Sophie. https://github.com/apache/kafka/pull/12856 "KAFKA-14392: KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms" just merged to trunk and seems like a potential candidate for 3.4.0 as it is a very small and targeted fix with very low risk. Could it be included even

Re: [DISCUSS] Apache Kafka 3.3.2

Hi Chris. https://github.com/apache/kafka/pull/12856 "KAFKA-14392: KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms" just merged to trunk and seems like a reasonable candidate for 3.3.2. Can it be included? Ron On Fri, Nov 18, 2022 at 10:57 AM Chris Egerton wrote: >

[jira] [Resolved] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-14392. --- Fix Version/s: 3.5.0 Resolution: Fixed > KRaft broker heartbeat timeout should not

Re: [DISCUSS] KIP-852 Optimize calculation of size for log in remote tier

Hi, Divij, Thanks for the reply. Is the new method enough for doing size-based retention? It gives the total size of the remote segments, but it seems that we still don't know the exact total size for a log since there could be overlapping segments between the remote and the local segments. You

Re: [Streams] GlobalStateManagerImpl#restoreState locally restores previously deleted records

Glad to hear you figured it out (and that it's not a KS bug :)). It's a contract in Kafka that serdes must do a `null <-> null` mapping. If that's not well documented / unclear, we should update the docs. Maybe

Re: [Streams] GlobalStateManagerImpl#restoreState locally restores previously deleted records

Patrick—Glad you got it cleared up, and good find re: empty byte[] vs null. KAFKA-7663 is very interesting. Just yesterday I thought of a use-case where supplying the processor for the Global State Store would be useful—what if you have an in-memory object that computes and caches aggregations of

[jira] [Created] (KAFKA-14464) Refactor MM2 connectors to make resource leaks from code defects less likely

Greg Harris created KAFKA-14464: --- Summary: Refactor MM2 connectors to make resource leaks from code defects less likely Key: KAFKA-14464 URL: https://issues.apache.org/jira/browse/KAFKA-14464 Project:

[jira] [Created] (KAFKA-14463) ConnectorClientConfigOverridePolicy is not closed at worker shutdown

Greg Harris created KAFKA-14463: --- Summary: ConnectorClientConfigOverridePolicy is not closed at worker shutdown Key: KAFKA-14463 URL: https://issues.apache.org/jira/browse/KAFKA-14463 Project: Kafka

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.3 #134

See Changes: -- [...truncated 419803 lines...] [2022-12-12T12:18:40.915Z] [2022-12-12T12:18:40.915Z] org.apache.kafka.streams.integration.StoreQueryIntegrationTest >

[jira] [Created] (KAFKA-14462) New Group Coordinator State Machine

David Jacot created KAFKA-14462: --- Summary: New Group Coordinator State Machine Key: KAFKA-14462 URL: https://issues.apache.org/jira/browse/KAFKA-14462 Project: Kafka Issue Type: Sub-task

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.4 #8

See

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

See

Re: [Streams] GlobalStateManagerImpl#restoreState locally restores previously deleted records

No it does not encrypt the keys. And it works fine for key like "bar" where the latest record on the topic is not a tombstone. But that got me thinking about how the values are actually written and read from kafka and I found the issue in my case, it was related to the serializer not writing

RE: [External] : Re: Kafka AdminClient DEFAULT_API_TIMEOUT_MS_CONFIG property not working as expected

Hi Luke, Yes our Admin creation was successful. Even though we have kept request.timeout.ms=100 there was no error or exception thrown. We used this admin to list out topics present in broker and it was successful. One thing I would like to point out is that we have created Admin not

Re: Kafka AdminClient DEFAULT_API_TIMEOUT_MS_CONFIG property not working as expected

Hi Shruti, Are you sure it creates admin client successfully after setting default.api.timeout.ms=2000 ? It should fail at this check: https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/admin/KafkaAdminClient.java#L618-L621 Try also set

[jira] [Resolved] (KAFKA-14379) consumer should refresh preferred read replica on update metadata

[ https://issues.apache.org/jira/browse/KAFKA-14379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-14379. - Fix Version/s: 3.3.2 Resolution: Fixed > consumer should refresh preferred read replica