Hi all,
I thought I'd call attention to one of the most visible deprecations
coming in 1.1.18: stonith-enabled. In order to deprecate that option,
we have to provide an alternate way to do the things that it does.
stonith-enabled determines whether a resource's "requires" meta-
attribute
Problem:
Under high write load, DRBD exhibits data corruption. In repeated tests over a
month-long period, file corruption occurred after 700-900 GB of data had been
written to the DRBD volume.
Testing Platform:
2 x Dell PowerEdge R610 servers
32GB RAM
6 x Samsung SSD 840 Pro 512GB (latest
Hi,
I'am using Pacemaker 1.1.15-11.el7_3.4 / Corosync 2.4.0-4.el7 under CentOS
7.3.1611
My subject is very close to the post "clearing failed actions" initiated by
Attila Megyeri in May 2017.
But the issue doesn't fit my case.
What I want to do is:
- 2 systemd resources running on