kfaraz commented on PR #18591: URL: https://github.com/apache/druid/pull/18591#issuecomment-3365370572
Thanks for the responses, @FrankChen021 , @GabrielCWT . Even though with the K8s task runner, the task pods are not technically a part of the Druid cluster, the Overlord still has to manage those tasks. The KubernetesTaskRunner itself keeps separate threads for each running task to track their status (this PR also updates that thread count, if I am not mistaken). So I should imagine that a major change in task capacity would also require some kind of scaling of the Overlord itself. Also, why is the Overlord restart "risky" or even "slow"? Doesn't a version upgrade require an Overlord restart too? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
