The is a spectrum for availability solutions, where you fit depends on what assumptions you can make about your application stack.
A more reliable way to receive notification of cluster events is coming in Pacemaker 1.1.14.
SBD can be particularly useful in environments where traditional fencing mechanisms are not possible.
It’s tempting to explain away some recovery scenarios, but it's not always appropriate.
The theory goes that pets have no place in the server room. Everything should be stateless and replicated. If one copy dies, who cares, there are 100 more.
As previously announced on RDO list and GitHub, we now have a way to allow Pacemaker to manage compute nodes within a single cluster while still allowing us ...
Anatomy of resource restart
Coming in 1.1.13 is a new option for location constraints: resource-discovery
As promised, this announcement brings the first release candidate for Pacemaker 1.1.12
It has come to my attention that the potential for data corruption exists in Pacemaker versions 1.1.6 to 1.1.9
With over 400 updates since the release of 1.1.10, its time to start thinking about a new release.
The good news is that as of Novemeber 1st, Pacemaker is now supported on RHEL 6.4 - with two caveats.
Unfortunately the current wire protocol used by pacemaker_remoted for exchanging messages was found to be suboptimal and we have taken the decision to change...
Announcing the release of Pacemaker 1.1.10
Announcing the seventh release candidate for Pacemaker 1.1.10