hi guys,
Is this below not the weirdest thing?
-> $ pcs constraint ref PGSQL-PAF-5435
Resource: PGSQL-PAF-5435
colocation-HA-10-1-1-84-PGSQL-PAF-5435-clone-INFINITY
colocation-REDIS-6385-clone-PGSQL-PAF-5435-clone-INFINITY
order-PGSQL-PAF-5435-clone-HA-10-1-1-84-Mandatory
order-PGSQL-PAF-5435-clone-HA-10-1-1-84-Mandatory-1
colocation_set_PePePe
Here Redis master should folow pgSQL master.
Which such constraint:
-> $ pcs resource status PGSQL-PAF-5435
* Clone Set: PGSQL-PAF-5435-clone [PGSQL-PAF-5435]
(promotable):
* Promoted: [ ubusrv1 ]
* Unpromoted: [ ubusrv2 ubusrv3 ]
-> $ pcs resource status REDIS-6385-clone
* Clone Set: REDIS-6385-clone [REDIS-6385] (promotable):
* Unpromoted: [ ubusrv1 ubusrv2 ubusrv3 ]
If I remove that constrain:
-> $ pcs constraint delete
colocation-REDIS-6385-clone-PGSQL-PAF-5435-clone-INFINITY
-> $ pcs resource status REDIS-6385-clone
* Clone Set: REDIS-6385-clone [REDIS-6385] (promotable):
* Promoted: [ ubusrv1 ]
* Unpromoted: [ ubusrv2 ubusrv3 ]
and ! I can manually move Redis master around, master moves
to each server just fine.
I again, add that constraint:
-> $ pcs constraint colocation add master REDIS-6385-clone
with master PGSQL-PAF-5435-clone
and the same...
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
