[jira] [Created] (KAFKA-14073) Logging the reason for creating a snapshot

dengziming created KAFKA-14073: -- Summary: Logging the reason for creating a snapshot Key: KAFKA-14073 URL: https://issues.apache.org/jira/browse/KAFKA-14073 Project: Kafka Issue Type: Improvemen

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

See Changes: -- [...truncated 568179 lines...] [2022-07-12T22:13:36.772Z] org.apache.kafka.streams.integration.StateDirectoryIntegrationTest > testNotCleanUpStateDirIfNot

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Thanks David! I think on the high level there are two meta points we need to concretize a bit more: 1) the migration path, especially the last step when clients flip the flag to enable the new protocol, in which we would have a window where both new protocols / rpcs and old protocols / rpcs are us

Re: [DISCUSS] KIP-709: Extend OffsetFetch requests to accept multiple group ids

Hi all, Following the PR discussion on this KIP's Admin API PR ( https://github.com/apache/kafka/pull/10964), we have changed the Admin API proposed in this KIP to use a separate ListConsumerGroupOffsetsSpec class to specify per-group spec including partitions for which offsets are fetched. The n

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

See Changes: -- [...truncated 568099 lines...] [2022-07-12T17:28:40.415Z] org.apache.kafka.streams.integration.StreamStreamJoinIntegrationTest > testLeft[caching enabled = fal

Re: [DISCUSS] KIP-837 Allow MultiCasting a Result Record.

Hi Sagar, I just finished reading the KIP and this seems to be a great addition. I agree with Matthias that the interface with a default implementation and deprecating partition() does seem cleaner. It has been a pattern that we have followed in the past. How I would handle a custom streams parti

Re: [VOTE] KIP-847

Thanks for the KIP, Artem. +1 Jun On Fri, Jul 8, 2022 at 12:41 AM David Jacot wrote: > Thanks, Artem. I am still +1. > > On Fri, Jul 8, 2022 at 3:45 AM Artem Livshits > wrote: > > > > Hello, > > > > There was an additional discussion and the KIP got changed as a result of > > that. I would li

[jira] [Resolved] (KAFKA-13968) Broker should not generator snapshot until been unfenced

[ https://issues.apache.org/jira/browse/KAFKA-13968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jose Armando Garcia Sancio resolved KAFKA-13968. Resolution: Fixed > Broker should not generator snapshot until bee

[jira] [Created] (KAFKA-14072) Crashed MirrorCheckpointConnector appears as running in REST API

Mickael Maison created KAFKA-14072: -- Summary: Crashed MirrorCheckpointConnector appears as running in REST API Key: KAFKA-14072 URL: https://issues.apache.org/jira/browse/KAFKA-14072 Project: Kafka

[jira] [Created] (KAFKA-14071) Kafka request handler threads saturated when moving a partition

Qinghui Xu created KAFKA-14071: -- Summary: Kafka request handler threads saturated when moving a partition Key: KAFKA-14071 URL: https://issues.apache.org/jira/browse/KAFKA-14071 Project: Kafka

[jira] [Created] (KAFKA-14070) queryMetadataForKey

Balaji Rao created KAFKA-14070: -- Summary: queryMetadataForKey Key: KAFKA-14070 URL: https://issues.apache.org/jira/browse/KAFKA-14070 Project: Kafka Issue Type: Improvement Components:

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.2 #59

See Changes: -- [...truncated 455440 lines...] [2022-07-12T12:45:53.097Z] > Task :connect:api:generateMetadataFileForMavenJavaPublication [2022-07-12T12:45:53.097Z] > Task :co

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi Ismael, Thanks for your feedback. Let me answer your questions inline. > 1. I think it's premature to talk about target versions for deprecation and > removal of the existing group protocol. Unlike KRaft, this affects a core > client protocol and hence deprecation/removal will be heavily depen

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi Justine, Thanks for your comments. Please find my answers below. - Yes, the new protocol relies on topic IDs with the exception of the topic names based in the ConsumerGroupHeartbeatRequest. I am not sure if using topic names is the right call here. I need to think about it a little more. Obvi

[jira] [Created] (KAFKA-14069) Allow custom configuration of foreign key join internal topics

Emmanuel Brard created KAFKA-14069: -- Summary: Allow custom configuration of foreign key join internal topics Key: KAFKA-14069 URL: https://issues.apache.org/jira/browse/KAFKA-14069 Project: Kafka

[jira] [Created] (KAFKA-14068) add node advertised listeners when AdminClient can not connect to the node

Justinwins created KAFKA-14068: -- Summary: add node advertised listeners when AdminClient can not connect to the node Key: KAFKA-14068 URL: https://issues.apache.org/jira/browse/KAFKA-14068 Project: Kafk

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

Hi Divij, Thanks for the KIP! I think it makes sense to delegate the responsibility of calculation to the specific RemoteLogMetadataManager implementation. But one thing I'm not quite sure, is that would the new `RemoteLogSizeBytes` metric be a performance overhead? Although we move the calculati