My Oracle Support Banner

Kafka Broker Fails to Start with "Exiting because log truncation is not allowed for partition" (Doc ID 2360426.1)

Last updated on SEPTEMBER 12, 2019

Applies to:

Big Data Appliance Integrated Software - Version 4.8.0 and later
Linux x86-64

Symptoms


The Kafka broker on given node does not complete startup.

The kafka-broker-<node_name>.log shows the following start up error:


2018-02-12 16:30:07,688 FATAL kafka.server.ReplicaFetcherThread: [ReplicaFetcherThread-0-130], Exiting because log truncation is not allowed for partition [<Topic Name>,<Partition Number>], Current leader 130's latest offset <xxx> is less than replica 131's latest offset <yyy>
2018-02-12 16:30:07,689 INFO kafka.server.KafkaServer: [Kafka Server 131], shutting down
2018-02-12 16:30:07,690 INFO kafka.server.KafkaServer: [Kafka Server 131], Starting controlled shutdown
2018-02-12 16:30:07,691 DEBUG org.apache.kafka.common.metrics.Metrics: Added sensor with name connections-closed:
...

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.