Mailing List Highlights

Updated 316 Days AgoPublic

Actions

This is a place to collect helpful tips from the ClusterLabs Mailing Lists.

Things to avoid

• ocf:anything: resource agent
• Mimicking traffic loss at Corosync level through putting the interface down (e.g. ifdown), especially when using redundant rings:
  • https://lists.clusterlabs.org/pipermail/users/2019-July/026111.html
  • https://lists.clusterlabs.org/pipermail/users/2019-March/016327.html
  • https://lists.clusterlabs.org/pipermail/users/2018-August/015561.html
  • https://lists.clusterlabs.org/pipermail/users/2017-March/005279.html
  • https://lists.clusterlabs.org/pipermail/users/2015-July/000878.html
  • See also Corosync and ifdown on active network interface

Advice

• Set clone options on the clone resource, not the resource being cloned
• Use the clone resource name in any constraints, rather than the resource being cloned
• Node attributes setting Q&A
• Fence timeouts summary
• Non-constraint start-up order factors

Limitations

• Live-migrateable resource will not migrate if it depends on a resource without that property
• Corosync's token timeout can (by design) delay failover upon fencing
• When does Pacemaker shoot other nodes in the head

Surprises

• Location constraints with infinite score do not limit resource to those nodes

Low-level topics

• dc-deadtime and startup-fencing options
• crm_simulate
• alerts

Humor (?)

• April Fools' Day 2016
• Bob Dylan strikes back
• April Fools' Day 2018