Re: [PR] Falkon SMS Kafka Usage [kafka-site]

mjsax merged PR #664: URL: https://github.com/apache/kafka-site/pull/664 -- 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: dev-unsubscr...@kafka.apache.or

Re: KRaft controller disaster recovery

Hi Jose and Colin, Thanks for your explanation! Yes, we all agree that 3 node quorum can only tolerate 1 node down. We just want to discuss, "what if" 2 out of 3 nodes are down at the same time, what can we do? Currently, the result is that the quorum will never form and all the kafka cluster is

Re: KRaft controller disaster recovery

Hi José, I think you make a valid point that our guarantees here are not actually different from zookeeper. In both systems, if you lose quorum, you will probably lose some data. Of course, how much data you lose depends on luck. If the last node standing was the active controller / zookeeper,

Re: Unexpected UNCLEAN leader election behaviour in KRaft vs. Zookeeper

Did you have unclean leader election enabled here? best, Colin On Mon, Apr 7, 2025, at 11:49, Julian Bergner wrote: > Hi, > We primarily operate a Kafka cluster consisting of 3 brokers (IDs: 4, > 5, 6) running Kraft in version 3.9.0. However, we tested the same > scenario in a Zookeeper-managed

Re: KRaft controller disaster recovery

Thanks Luke. On Thu, Apr 3, 2025 at 7:14 AM Luke Chen wrote: > In addition to the approaches you provided, maybe we can have a way to > "force" KRaft to honor "controller.quorum.voters" config, instead of > "controller.quorum.bootstrap.servers", even it's in kraft.version 1. Small clarification.

Re: KRaft controller disaster recovery

HI Juha, That's for the discussion. On Thu, Apr 3, 2025 at 4:08 AM Juha Mynttinen wrote: >Consider the following Kafka controller setup. There are three controllers > c1, c2 and c3, each on its own hardware. All controllers are voters and > let’s assume c1 is the leader. Assume new servers can b

Re: [DISCUSS] Git commits and metadata

Thanks David. On Thu, Mar 27, 2025 at 9:50 AM David Arthur wrote: > Commented-by: left any comment on the PR (any contributor) > Reviewed-by: did a full review on the PR (any contributor) > Approved-by: committer(s) who approved the PR This matches my understanding and captures contributors' int

[jira] [Created] (KAFKA-19104) Support metadata version downgrade in Kafka

Colin McCabe created KAFKA-19104: Summary: Support metadata version downgrade in Kafka Key: KAFKA-19104 URL: https://issues.apache.org/jira/browse/KAFKA-19104 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-19103) Remove OffsetConfig

Chia-Ping Tsai created KAFKA-19103: -- Summary: Remove OffsetConfig Key: KAFKA-19103 URL: https://issues.apache.org/jira/browse/KAFKA-19103 Project: Kafka Issue Type: Improvement R

[jira] [Created] (KAFKA-19102) Enhance the docs of group.coordinator.append.linger.ms

Chia-Ping Tsai created KAFKA-19102: -- Summary: Enhance the docs of group.coordinator.append.linger.ms Key: KAFKA-19102 URL: https://issues.apache.org/jira/browse/KAFKA-19102 Project: Kafka Is

[jira] [Resolved] (KAFKA-19098) Remove lastOffset from PartitionResponse

[ https://issues.apache.org/jira/browse/KAFKA-19098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-19098. Fix Version/s: 4.1.0 Resolution: Fixed > Remove lastOffset from PartitionResponse >

RE: [DISCUSS] KIP-1121: Compression acceleration in Kafka

Hi Greg, I have refactored the proposal to reduce the API surface area. I introduced a new CompressionService interface which contains basic compression/decompression functions. A service provider, when supplied, would be wrapped in a concrete 'Compression' and run similar to the existing compr

Re: [DISCUSS] KIP-1066: Mechanism to cordon brokers and log directories

Hi Jun, 10: Yes that's good idea. I've added that to the KIP. 11: Yes that was my plan. We need to check the metadata version and reject updates to the configuration is the metadata version is too low. I clarified that in the KIP. Did you have anything else in mind (if you can remember what you t

[jira] [Created] (KAFKA-19100) Use ProcessRole.toString instead of String in AclApis

黃竣陽 created KAFKA-19100: --- Summary: Use ProcessRole.toString instead of String in AclApis Key: KAFKA-19100 URL: https://issues.apache.org/jira/browse/KAFKA-19100 Project: Kafka Issue Type: Task

[jira] [Created] (KAFKA-19099) Remove GroupSyncKey, GroupJoinKey, and MemberKey

Chia-Ping Tsai created KAFKA-19099: -- Summary: Remove GroupSyncKey, GroupJoinKey, and MemberKey Key: KAFKA-19099 URL: https://issues.apache.org/jira/browse/KAFKA-19099 Project: Kafka Issue Ty

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.9 #181

See

[jira] [Resolved] (KAFKA-19084) Port KAFKA-16224 for acknowledgements in ShareConsumers.

[ https://issues.apache.org/jira/browse/KAFKA-19084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivsundar R resolved KAFKA-19084. -- Resolution: Fixed > Port KAFKA-16224 for acknowledgements in ShareConsumers. > ---

Re: [DISCUSS] KIP-1152: Add transactional ID prefix filter to ListTransactions API

Hi Calvin, Thanks for the update. DJ03: I wonder whether we should call it `TransactionalIdPattern`. Filter is a bit redundant in my opinion. DJ04: The response could now return `INVALID_REGULAR_EXPRESSION` error if the regex is invalid. DJ05: Should we say that all transactions are returned if

Re: [VOTE] KIP-1123: Rack-aware partitioning for Kafka Producer

Hi, Maybe someone else wants to have a look? Best, Ivan On Mon, Mar 31, 2025, at 14:07, Federico Valeri wrote: > +1 non binding > > On Mon, Mar 24, 2025 at 9:51 AM Frédérik Rouleau > wrote: > > > > +1 (non-binding) > > > > On Sat, Mar 22, 2025 at 12:32 PM Ivan Yurchenko wrote: > > > > > Hi! >