Refactor #27412
closed
Ensure not multiple orchestrators can run at once
Added by Ivan Necas over 5 years ago.
Updated over 5 years ago.
Description
The new sidekiq approach expects only one orchestrator process to be running. We should do checking (probably via the current dynflow locking mechanism) to enforce it to avoid some weird states when multiple orchestrators would be running at the same time.
- Blocks Tracker #27408: Dynflow workers extraction to separate processes added
- Status changed from New to Ready For Testing
- Assignee set to Adam Ruzicka
- Pull request https://github.com/Dynflow/dynflow/pull/335 added
The PR allows us to run the orchestrator in active-passive mode. It means the requirement changes a bit, we can run multiple orchestrators, but only one can be in active mode per redis instance and/or namespace. There is no limit on the number of passive ones.
- Target version set to dynflow-1.4.0
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF
Updated by 
Updated by