Pacemaker: Difference between revisions
From DWIKI
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
uses [[Corosync]] or [[heartbeat]], it seems corosync is the one to go for. | uses [[Corosync]] or [[heartbeat]], (it seems) corosync is the one to go for. | ||
=Links= | =Links= | ||
| Line 10: | Line 10: | ||
*[http://djlab.com/2013/04/pacemaker-corosync-drbd-cheatsheet/ Cheatsheet] | *[http://djlab.com/2013/04/pacemaker-corosync-drbd-cheatsheet/ Cheatsheet] | ||
*[https://www.freesoftwareservers.com/wiki/pcs-tips-n-tricks-constraints-delete-resources-3965539.html PCS tips&tricks] | *[https://www.freesoftwareservers.com/wiki/pcs-tips-n-tricks-constraints-delete-resources-3965539.html PCS tips&tricks] | ||
*[http://www.nashville-linux-guy.com/index.php/blog/45-centos-7-active-active-iscsi-cluster also useful pcs tips] | |||
=Notes= | =Notes= | ||
Revision as of 15:31, 13 April 2018
uses Corosync or heartbeat, (it seems) corosync is the one to go for.
Links
- Cluster Labs
- Pacemaker explained
- Building a high-available failover cluster with Pacemaker, Corosync & PCS
- HIGH AVAILABILITY ADD-ON ADMINISTRATION
- How To Create a High Availability Setup with Corosync, Pacemaker, and Floating IPs on Ubuntu 14.04
- http://fibrevillage.com/sysadmin/304-pcs-command-reference
- Cheatsheet
- PCS tips&tricks
- also useful pcs tips
Notes
by specifying -INFINITY, the constraint is binding.
Commands/tools
- crm
- crmadmin
- cibadm
- pcs
- corosync
Useful commands
Dump entire crm
cibadm -Q
FAQ
show detailed resources
pcs resource --full
stop node
pcs cluster standby node-1
set maintenance mode
pcs property set maintenance-mode=true
show virtual ip
pcs resource show IPv4_BIND
Error: cluster is not currently running on this node
pcs cluster start
Remove a constraint
pcs constraint list --full
to identify the constraints and then
pcs constraint remove <whatever-constraint-id>
Clear error messages
pcs resource cleanup
Call cib_replace failed (-205): Update was older than existing configuration
can be run only once
[Error signing on to the CIB service: Transport endpoint is not connected ]
probably selinux
debug resource
pcs resource debug-start resource
*** Resource management is DISABLED *** The cluster will not attempt to start, stop or recover services
??
