jreyeshdez commented on issue #15942: URL: https://github.com/apache/druid/issues/15942#issuecomment-2515150650
> The code that creates the config map is in a downstream kubernetes java library that has been updated in #15449. We use the druid-operator to deploy our clusters but this issue is not related to how it is deployed, it's controlled exclusively by the k8s extension. If the config maps get recreated with the old format again then you must have a version 28 version of one or more of the processes running somewhere. If you have 3 replicas perhaps the helm rolling update does them one at a time leaving old code running. The other thing you could try is manually editing the date in the config map to the new format which would move the error to the older versions whilst the new ones rollout. If you want a hand, reach out to me In that cluster, there is only 1 Druid cluster running, it is isolated in a AWS dev account and EKS. However there are replicas for broker (3), coordinator (3) and router (3). Only 1 historical. Also worth noting it is running in mm-less and zk-less, not sure if that over complicates it. I think it might be related to the rolling update where if the newer upcoming pod fails to start then it won't terminate the other ones with old config. So not sure what best approach I can take here, specially when I have to do it to the production cluster. -- 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]
