You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of scale down on redis uses the instant failover (in case of primary scale down) that happened before the fix.
If redis is deployed on agent version 2.9.43, and a scale down operation is executed on the primary, redis server will elect a new primary, but sentinel doesn't get a proper SENTINEL RESET to relearn the status of the deployment.
The text was updated successfully, but these errors were encountered:
With the release of this fix for juju: https://bugs.launchpad.net/juju/+bug/1951415 scaling down operations now don't immediately terminate the pod.
The current implementation of scale down on redis uses the instant failover (in case of primary scale down) that happened before the fix.
If redis is deployed on agent version
2.9.43
, and a scale down operation is executed on the primary, redis server will elect a new primary, but sentinel doesn't get a properSENTINEL RESET
to relearn the status of the deployment.The text was updated successfully, but these errors were encountered: