Open funky-eyes opened 1 week ago
Restarting does not resolve this issue. The only solution is to delete the log folder corresponding to the replica where the log segment anomaly occurred and then resynchronize from the leader.
I'm not sure whether this is a Kafka bug or a bug in the tiered storage plugin, so I have also reported it to the Kafka community. https://issues.apache.org/jira/browse/KAFKA-17020
What happened?
After enabling tiered storage, occasional residual logs are left in the replica. Based on the observed phenomenon, the index values of the rolled-out logs generated by the replica and the leader are not the same. As a result, the logs uploaded to S3 at the same time do not include the corresponding log files on the replica side, making it impossible to delete the local logs.
leader config:
replica config:
topic config:
What did you expect to happen?
What else do we need to know?