Change Details

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 and the :0 instance moved, resulting in unnecessary downtime. See: * [[https://issues.redhat.com/browse/RHEL-70029 | RHEL-70029]]

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: * [[https://issues.redhat.com/browse/RHEL-70029 | RHEL-70029]]

RThe 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, the :1 instance will be stopped and the :0 instance moved,before it is known whether they will remain active. resulting in unnecessary downtimeIt might be possible to consider the :0 instance orphaned instead of the :1 one. See: * [[https://issues.redhat.com/browse/RHEL-70029 | RHEL-70029]]