sbd
sbd copied to clipboard
ClusterLabs
Shared-storage based fencing
Not foreseen to be pulled as is!!! Just for discussion... Further reading on the topic: https://bugzilla.redhat.com/show_bug.cgi?id=1377724
As the name says focus is bringing sbd from a forking model to either 'simple' or 'notice' start-model in systemd. Discussion started off in #134. PR atm still contains changes...
- prevent possible lockup when format in proc changes - properly get and handle scheduler policy & prio - recognize and try to handle cgroup-v2 similarly - on SCHED_RR failing...
This is an universal solution to prevent fencing from hanging on silently blocked devices as originally brought up from https://github.com/ClusterLabs/sbd/pull/119.
Fix: agent: prevent fencing from hanging on sbd commands if any of the devices is silently blocked
If any of the configured SBD devices is silently blocked without any explicit I/O error from kernel, fencing will get stuck and time out, even if the majority of the...
Currently, if `SBD_SYNC_RESOURCE_STARTUP=false` and `SBD_PACEMAKER=false`, sbd prints a warning every time it runs: "Should think about enabling SBD_SYNC_RESOURCE_STARTUP." But this warning can never be addressed, since `SBD_SYNC_RESOURCE_STARTUP=true` doesn't work with...
When CMAP disconnects sbd results in 100% CPU usage. This patch is currently used on SUSE, so upstreaming seem reasonable.
1) Currently the only hard errors are: - sbd binary is not existing or not executable. - 'TimeoutStartSec' of service is shorter than 'msgwait' if 'SBD_DELAY_START' is enabled. - 'TimeoutStartSec'...
If cluster connection is lost, exit sbd-cluster and let the inquisitor handle the reconnect by restart.
