A DCM migration in progress may terminate unexpectedly, and we need to determine how to restart a migration correctly.
Migrations will be kicked off as needed when the moose application starts up. What happens when moose applications are scaled in a cluster and several instances try to start/restart a migration?
In the past, I've addressed these challenges using Redis atomic keys to understand state across microservices.
linear[bot]
commented
6 months ago
A DCM migration in progress may terminate unexpectedly, and we need to determine how to restart a migration correctly.
Migrations will be kicked off as needed when the moose application starts up. What happens when moose applications are scaled in a cluster and several instances try to start/restart a migration?
In the past, I've addressed these challenges using Redis atomic keys to understand state across microservices.