Hello Dayo,
This is a known issue, since today Kafka's log rolling / cleaning policy
depends on the creation timestamp of the segment files, which could be
modified upon partition migration / broker restart, it can cause the server
to not honor the specified log cleaning config. Some more details
Hi,
I've noticed an interesting behaviour which I hope someone can fully
explain.
I have 3 Kafka Node cluster with a setting of log.retention.hours=168 (7
days) and log.segment.bytes=536870912.
I recently restarted one of the nodes and it's uptime is now 3 days behind
than the other 2.
After abo
