Closed CoinCoderBuffalo closed 2 weeks ago
I made one configuration change to the indexer.runner.type and the behavior is different now:
# Configure this coordinator to also run as Overlord
druid.coordinator.asOverlord.enabled=true
druid.coordinator.asOverlord.overlordService=druid/overlord
druid.indexer.queue.startDelay=PT30S
druid.indexer.runner.type=remote
The kafka tasks still respawn every hour, but they succeed this time. Is this normal behavior to have kafka tasks respawn? It didn't behave this way in previous versions of Druid.
This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.
Affected Version
apache/druid:25.0.0
Description
I'm running Druid in Kubernetes with the Druid Operator. I create 7 Kafka Supervisors. This in turn creates 7 Kafka indexing tasks. These all work fine for about an hour, then the 7 Kafka tasks get duplicated for some reason in a "pending" status and a little later the original 7 tasks change to "failed".
Original 7 running fine for an hour:![image](https://github.com/apache/druid/assets/3186418/51354be2-2f98-4e34-a97c-4bcd049d3eae)
After 1 hour 7 duplicates created somehow all in a "pending" status:![image](https://github.com/apache/druid/assets/3186418/16ced4f5-c237-4597-ba21-384dbee13e90)
About 10 minutes later all are in a "failed" state:
I've checked the coordinator and middlemanager logs and don't see any problems reported.
Coordinator log sample:
middle manager log sample:
middleManagers config: