Migrate exclusive lease keys from Redis persistent to redis-cluster-persistent
As there are quite a high volume of set and del for exclusive lease keys in #2155 (comment 1470006052), we can move them to a new redis-cluster
which will serve as the new Redis Cluster counterpart of Redis Persistent.
To execute this migration, no additional infrastructure needs to be provisioned. The bulk of the work is to be done on the application side.
A concern would be the release for SM customers since they would not have a feature-flag-based deployment. Since we are migrating to the new redis cluster persistent, this will not affect SM users.
Another thing to note is that this problem will need to be resolved even if we decide to keep exclusive lease keys in SharedState
for SaaS as we will be migrating SharedState
out of Redis persistent, into a Redis Cluster in &1055 (closed).
Milestones
- Provisioning new
redis-cluster-persistent
- Ensure that the application is ready for migration (gitlab-org/gitlab!128083 (merged))
- Perform migration of exclusive lease keys