How do we access the Kafka journal when facing pods in a CrashLoopBackOff?

Solution Verified - Updated -

Issue

We encounter that the Kafka Pod's Persistence Volume has reached its limit and the pod log shows:

xxxx-xx-xx xx:xx:xx,xxx ERROR [KafkaServer id=0] Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer) [main]
org.apache.kafka.common.errors.CorruptRecordException: Found record size 0 smaller than minimum record overhead (14) in file /var/lib/kafka/data/kafka-log0/xxxxx/xxx###.log.

The pod is in CrashLoopBackOff; how do we access the PV and recover the cluster?

Environment

Red Hat AMQ Streams

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content