On Wed, May 9, 2018 at 6:26 AM, Andrew Price wrote:
> [linux-cluster@ isn't really used nowadays; CCing users@clusterlabs]
>
> On 08/05/18 12:18, Jason Gauthier wrote:
>>
>> Greetings,
>>
>> I'm working on a setup of a two-node cluster with shared storage.
>> I've been
Was trying to simulate the "Corosync main process was not scheduled for xx
ms" issue.
Have a 2 node cluster with with a clone resource(Master-Slave).
*TEST #1*
Initially state of cluster resource:
NodeA - Master
NodeB - Slave
Current DC - NodeA
Now I freeze the corosync main
On Tue, 2018-05-08 at 23:52 +0800, lkxjtu wrote:
> I have a three node cluster of about 50 resources. When I reboot
> three nodes at the same time, I observe the resource by "crm status".
> I found that pacemaker starts 3-5 resources at a time, from top to
> bottom, rather than start all at the
[linux-cluster@ isn't really used nowadays; CCing users@clusterlabs]
On 08/05/18 12:18, Jason Gauthier wrote:
Greetings,
I'm working on a setup of a two-node cluster with shared storage.
I've been able to see the storage on both nodes, and appropriate
configuration for fencing the bock