Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redis cluster inservice upgrade is not working with zero downtime #90

Open
TANISH-18 opened this issue Feb 1, 2023 · 1 comment
Open

Comments

@TANISH-18
Copy link

While doing the Redis cluster in-service upgrade from older chart to newer chart. Redis operator is performing the Rolling update shard by shard which is fine.
but in one shard it is upgrading the master replicas at once due to which there is disconnection with the application.

can we improve the Rolling update logic such that first it upgrade the replicas of one shard then promote that replica to master and then we upgrade master and new master will join back as replica.?

@TANISH-18
Copy link
Author

(

func (c *Controller) manageRollingUpdate(ctx context.Context, admin redis.AdminInterface, cluster *rapi.RedisCluster, rCluster *redis.Cluster, oldNodes, newNodes redis.Nodes) error {
)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant