Okay thanks for the update Dave. We’ve applied the workaround on container start and it does the job for now.
Thanks Gerroald,
This solution appears to work for a single pod. Unfortunately this seems to work only for the pod in which the command is executed and doesn’t affect all pods sharing a common DB. It also must be reapplied whenever pods are rescheduled, restarted, or the deployment scaled out. We’re running multiple pods for HA / performance and autoscaling according to load.
We can workaround by applying this on container start, but is there any way to store this configuration option that will persist in the above scenarios?
Further to the above, it seems it’s possible to fix buckets after a move by running the Sync command from WP Stateless settings.
Is there any way of calling this function in an automation environment – API, wp-cli etc?
