I decided to do another release candidate, because we had a large
number of changes since rc3. The fourth release candidate for Pacemaker
version 1.1.18 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.18-
rc4
The big changes are numerous scalability improv
On 02.11.2017 23:08, Dennis Jacobfeuerborn wrote:
> Hi,
> I'm setting up a redundant NFS server for some experiments but almost
> immediately ran into a strange issue. The drbd clone resource never
> promotes either of the to clones to the Master state.
>
> The state says this:
>
> Master/Slave
Hi,
I'm setting up a redundant NFS server for some experiments but almost
immediately ran into a strange issue. The drbd clone resource never
promotes either of the to clones to the Master state.
The state says this:
Master/Slave Set: drbd-clone [drbd]
Slaves: [ nfsserver1 nfsserver2 ]
met
On 31.10.2017 12:58, Ferenc Wágner wrote:
> Dennis Jacobfeuerborn writes:
>
>> if I create a new unit file for the new file the services would not
>> depend on it so it wouldn't get automatically mounted when they start.
>
> Put the new unit file under /etc/systemd/system/x.service.requires to
>
Replying to myself:
On Wed, 11 Oct 2017, Jean-Marc Saffroy wrote:
> I am caught by surprise with this behaviour of DLM:
> - I have 5 nodes (test VMs)
> - 3 of them have 1 vote for the corosync quorum (they are "voters")
> - 2 of them have 0 vote ("non-voters")
>
> So the corosync quorum is 2.
>
>>> Ferenc Wágner schrieb am 27.10.2017 um 07:41 in Nachricht
<87o9otxi4e@lant.ki.iif.hu>:
> Norberto Lopes writes:
>
>> colocation backup-vip-not-with-master -inf: backupVIP postgresMS:Master
>> colocation backup-vip-not-with-master inf: backupVIP postgresMS:Slave
>>
>> Basically what's occ
