Re: broker crashing when running in raft mode

Seems that actually running ./bin/kafka-reassign-partitions.sh to first generate and then execute to move the topic is working. I later realized that in a cluster where the metadata have been migrated to k-raft, the following command: ./bin/kafka-topics.sh --describe --bootstrap-server

Re: 回复: Request to be added to kafka contributors list

Did you sign out and sign in again? On 5/17/24 9:49 AM, Yang Fan wrote: Thanks Matthias, I still can't find "Assign to me" button beside Assignee and Reporter. Could you help me set it again? Best regards, Fan 发件人: Matthias J. Sax 发送时间: 2024年5月17日 2:24 收件人:

broker crashing when running in raft mode

I'm trying to finish the migration of a dev cluster that used to use ZK. I finished the migration of Metadata from ZK to raft and it completed fairly fast. I did notice an error message: * java.lang.RuntimeException: The log dir

回复: Request to be added to kafka contributors list

Thanks Matthias, I still can't find "Assign to me" button beside Assignee and Reporter. Could you help me set it again? Best regards, Fan 发件人: Matthias J. Sax 发送时间: 2024年5月17日 2:24 收件人: users@kafka.apache.org 主题: Re: Request to be added to kafka contributors

Re: JMX Metrics UnderReplicatedPartitions And UnderMinIsrPartitionCount

Hi Artem, yes that's exactly the case! We're using Spring Kafka 2.7 and the @RetryableTopic has a default replication factor of 1 but our broker is configured with minIsr=2. In Spring Kafka 3 they changed it to -1 (meaning broker default value) [0]. Thanks! Andi [0]

Re: JMX Metrics UnderReplicatedPartitions And UnderMinIsrPartitionCount

Hi, this could be the case if you have a topic with min.insync.replicas > replication factor. On Fri, May 17, 2024 at 10:37 AM Andi Büchler wrote: > Hello, > > using the JmxTool I discovered that one can have _no_ under replicated > partitions, but have an under minISR partition count > 0.

JMX Metrics UnderReplicatedPartitions And UnderMinIsrPartitionCount

Hello, using the JmxTool  I discovered that one can have _no_ under replicated partitions, but have an under minISR partition count > 0. Does anyone know, how that can be? I was expecting that when a partition is below the minimum in sync replica count, it would be defined as under

Kafka Broker monitoring

Hi Team, We have some Splunk dashboards along with custom UI elements to report Kafka health status. We forward all Kafka health check statuses to be loaded into Splunk. However, we are encountering capacity issues on Splunk as we service multiple Kafka clusters across our data center as well