Page MenuHomeClusterLabs Projects

When lowering clone-max on an anonymous clone, ensure instances that will remain active don't restart
Open, LowPublic

Assigned To
None
Authored By
kgaillot
Mon, Dec 23, 6:07 PM
Tags
  • Restricted Project
  • Restricted Project
  • Restricted Project
Referenced Files
None
Subscribers

Description

The reproducer is an asymmetric two-node cluster with an anonymous clone with clone-max=2, and location constraints enabling the clone on each node. The location constraint for the node running the :0 instance is removed, and clone-max is lowered to 1. In that case, the :1 instance will be stopped on the remaining node and the :0 instance will be moved there, resulting in unnecessary downtime.

This might be tricky since instances must be numbered when reading history, before it is known whether they will remain active. It might be possible to consider the :0 instance orphaned instead of the :1 one.

See:

Event Timeline

kgaillot created this task.
kgaillot created this object with edit policy "Restricted Project (Project)".
kgaillot renamed this task from When lowering clone-max on an anonymous clone, ensure active instances get lowest instance numbers to When lowering clone-max on an anonymous clone, ensure instances that will remain active get lowest instance numbers.Mon, Dec 23, 6:14 PM
kgaillot renamed this task from When lowering clone-max on an anonymous clone, ensure instances that will remain active get lowest instance numbers to When lowering clone-max on an anonymous clone, ensure instances that will remain active don't restart.Mon, Dec 23, 6:20 PM
kgaillot updated the task description. (Show Details)