We have seen an exception caused by shutting down scheduler before shutting down LogManager.
When LogManager was closing partitons one by one, scheduler called to delete old segments due to retention. However, the old segments could have been closed by the LogManager, which subsequently marked logdir as offline and didn't write the clean shutdown marker. Ultimately the broker would take hours to restart.
- is duplicated by
KAFKA-13070 LogManager shutdown races with periodic work scheduled by the instance
- links to