c8f5fdfc36
A resource lock is used as a synchronization point between pacemaker cluster nodes. It is currently implemented by adding an attribute in an offline copy of CIB, and merging the update in the CIB only if no concurrent updates has occurred in the mean time. The problem with that approach is that - even if the concurrency is enforced by pacemaker - the offline CIB contains a snapshot of the cluster state; so pushing back the entire offline CIB pushes old resources' state back into the cluster. This causes additional burden on the cluster and sometimes caused unexpected cluster state transition. Reimplement the locking strategy with cibadmin; It's a much faster approach, that provides the same concurrency guarantees, and only changes one attribute rather than the entire CIB, so it doesn't cause unexpected cluster state transition. Closes-Bug: #1905585 Change-Id: Id10f026c8b31cad7b7313ac9427a99b3e6744788 |
||
|---|---|---|
| .. | ||
| monitoring | ||
| tests | ||
| __init__.py | ||
| nova_statedir_ownership.py | ||
| nova_wait_for_api_service.py | ||
| nova_wait_for_compute_service.py | ||
| pacemaker_mutex_restart_bundle.sh | ||
| pacemaker_resource_lock.sh | ||
| pacemaker_restart_bundle.sh | ||
| pacemaker_wait_bundle.sh | ||
| placement_wait_for_service.py | ||
| pyshim.sh | ||
| wait-port-and-run.sh | ||