I have 6 broker cluster.

I upgraded it from 0.8.1.1 to 0.10.0.0.

Kafka Producer to cluster to consumer (apache storm) upgrade went smooth
without any errors.
Initially keeping protocol to 0.8 and after clients were upgraded it was
promoted to 0.10.

Out of 6 brokers, 3 are honouring  log.retention.hours. For other 3 when
broker is restarted the time stamp for segment changes to current time.
That leads to segments not getting deleted hence disk gets full.

du -khc /disk1/kafka-broker/topic-1

71G     /disk1/kafka-broker/topic-1

71G     total

Latest segment timestamp : May 25 07:34

Oldest segment timestamp : May 25 07:16


It is impossible that 71 GB data was collected in mere 15 mins of
time. The log.retention.hours=24
and this is not new broker so oldest data should be around 24 hrs old.

As mentioned above only 3 out of 6 are showing same behaviour.  Why is this
happening ?

Reply via email to