kfaraz commented on PR #17738: URL: https://github.com/apache/druid/pull/17738#issuecomment-2790049893
> @kfaraz That's true. But if the namespace of overlord changes, I'm wondering why do we need to change the overlord namespace during a rolling update? @FrankChen021 , I am thinking of a case slightly different from the one discussed in the description. Say a Druid cluster is running in namespace C1 and its launching task pods in namespace X. Assume there is no other cluster launching task pods in X. Currently, the Overlord is able to retrieve all peon jobs from namespace X and process them properly. Now, before we setup another cluster that can launch task pods in X, we must set the new property `druid.indexer.runner.overlordNamespace` on Druid C1 Overlord. But as soon as we restart this Overlord, it will lose track of any of the peon jobs it might have just launched because they don't have the required label. -- 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]
