FrankChen021 commented on PR #17738: URL: https://github.com/apache/druid/pull/17738#issuecomment-2790101165
I understand your concern. The root problem here is that the `namespace` where the task is running is used as a configuration at overlord, however I would like see this information as part of task's metedata which should be saved in the tasks' metadata storage. If we keep the namespace information of a running task in the task metadata storage, this can be solved, and unlock other possibilities like we can deploy overlord in two K8S in different IDCs to serve as HA, tasks started by overlord 1 can be managed by overlord 2 if it becomes leader later. -- 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]
