This message was deleted.
# troubleshooting
s
This message was deleted.
i
this is what I see in log of the task itself it finishes successfully, there is some error connected to lookups but probably connected to shutdown sequence
v
I have seen this when there was a firewall on the machine running the task (the firewall was left enabled on one node out of many and it took a while to track that down). Does this happen on a specific node?
i
thanks @Vijay Narayanan I will check once again firewall settings. maybe it’s some sporadical flips of some rules…not sure. It’s not happening all the time but only once in a while. Let me understand this better: you are saying that this kind of problems might happen because of some connectivity issues between node executing peon task(middle manager) and coordinator?
v
yes. If the task is not able to communicate with the overlord.
i
ok, thanks. Are there any configs for retries/backoff policy etc?
@Vijay Narayanan hmm, looking at peon logs once again I see 2023-01-12T022051,924 INFO [main] org.apache.druid.indexing.overlord.SingleTaskBackgroundRunner - Starting graceful shutdown of task[index_kafka_sp_campaigns_realtime_aggregation_cdce20b447c1666_ghjeoknb]. 2023-01-12T022051,924 INFO [main] org.apache.druid.indexing.seekablestream.SeekableStreamIndexTaskRunner - Stopping gracefully (status: [PUBLISHING]) 2023-01-12T022051,924 INFO [main] org.apache.druid.indexing.overlord.SingleTaskBackgroundRunner - Graceful shutdown of task[index_kafka_sp_campaigns_realtime_aggregation_cdce20b447c1666_ghjeoknb] finished in 0ms. For me it seems like the part of talking with overload finished successfully, what I”m missing?
v
can you paste the full overlord log here?
is this happening only with tasks on a specific node?
i
it’s happening from time to time from all middle manager’s nodes
v
looking at the log I am seeing rg.apache.druid.indexing.overlord.TaskQueue - Failed to persist status for task…..do you see any metastore errors in the rest of the log
i
checking
yes, I see 4 such errors today
“apache.druid.indexing.overlord.TaskQueue - Failed to persist status for task”
looking at previous dates, it’s always 2-4 such errors per day
v
if the overlord leader has changed after the task started then this may happen….is the overlord restarting frequently?
i
I’ll check this
thanks
v
if you have a lot of tasks check the heap size on the overlord and consider increasing it.
i
any other options? I’m looking at heap usage, and it seems normal, gc is low the process running from 19Dec, so it’s not restarted recently
v
The other possibility is an issue with zookeeper and the communication with zookeeper. Which version of druid is this?
i
We are using 24.0.1. I will check zookeeper metrics, might be something there thanks a lot!
it seems to me that this one is very close to what we are experiencing https://www.druidforum.org/t/kafka-ingestion-peon-tasks-success-but-overlord-shows-failure/7374/28 I’ll try to check options and relevant metrics