This message was deleted.
# troubleshootings
Slackbot
05/04/2023, 7:23 PMThis message was deleted.
s
Sergio Ferragut
05/04/2023, 8:17 PMOn larger clusters, the coordinator and overlord are usually deployed separately. Adding more of them helps for high availability but only one of them is ever the leader.
A couple of ideas on what to check:
• do you have enough capacity to run 121 tasks concurrently, if there are not enough worker slots, the controller process will timeout and fail.
• Is this on kubernetes? If the coordinator/overlord is failing and there are no errors, perhaps it is exceeding its memory/cpu limit and getting killed by kubernetes. Are the jvm settings in line with the pod resources?
• How busy was the coordinator node in terms of CPU and memory when it failed? Does it have enough resources?
a
Abhishek Agarwal
05/05/2023, 6:32 AMwhat version are you on?
Abhishek Agarwal
05/05/2023, 6:34 AMI agree with Sergio that your master nodes do seem underprovisioned for the number of workers you are running.
b
Bharat Kumar Singh
05/08/2023, 8:31 AMHey @Sergio Ferragut @Abhishek Agarwal Thanks for helping.
Using a bigger node for master server helped me here.
Btw my druid version is 25.0.0 and its on kubernetes.