<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kafka on Lead DevOps</title><link>https://lead-devops.blackdevhub.online/en/tags/kafka/</link><description>Recent content in Kafka on Lead DevOps</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 31 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lead-devops.blackdevhub.online/en/tags/kafka/index.xml" rel="self" type="application/rss+xml"/><item><title>Kafka: Cluster Health Check</title><link>https://lead-devops.blackdevhub.online/en/posts/kafka-cluster-health-check/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><guid>https://lead-devops.blackdevhub.online/en/posts/kafka-cluster-health-check/</guid><description>&lt;p&gt;A Kafka cluster in KRaft mode doesn&amp;rsquo;t forgive neglect until the first incident. Health checks need to be regular and quick — no graphs or dashboards, just the terminal. Here&amp;rsquo;s the command set that covers the typical checklist: processes, quorum, partition leaders, ISR, and a quick status report in one shot.&lt;/p&gt;&#10;&lt;h2 id="checking-kraft-processes"&gt;Checking KRaft Processes&#10;&lt;/h2&gt;&#10;&lt;p&gt;KRaft mode has no separate ZooKeeper — the &lt;code&gt;controller&lt;/code&gt; role is either co-located with the broker or isolated on dedicated nodes. First, verify the JVM processes are alive and see which mode each node started in.&lt;/p&gt;</description></item></channel></rss>