Open
Description
Affected Version
0.22.1
Description
What happened?
- Druid did not remove segments from middle manager after the ingestion task failed
Background
- For some reason, some Kafka ingestion tasks at some point failed. We saw InterruptedExceptions in the logs.
- We are thinking it is likely due to some overlord failure.
- The tasks reran and they auto recovered.
Question
- One of the ingestion task that failed may have created some realtime segments that got interrupted. Those segments did not get removed from middle manager.
- Is this behavior expected? If the tasks auto recovered, such stray segments should also have been deleted but they continued to stay on middle manager.