> On 27 Jan 2015, at 9:57 pm, Vladislav Bogdanov wrote:
>
> Hi,
>
> Playing with two-week old git master on a two-node cluster I discovered that
> only limited set of "notify" operations is performed for clone and
> master-slave instances when all of them are being started/stopped.
>
> Clone
> On 23 Jan 2015, at 9:13 am, brook davis wrote:
>
> < snip >
>> It sounds like default-resource-stickiness does not kick in; and with
>> default resource-stickiness=1 it is expected (10 > 6). Documentation
>> says default-recource-stickiness is deprecated so may be it is ignored
>> in your ver
> On 10 Feb 2015, at 6:50 pm, d tbsky wrote:
>
> hi:
> I was using pacemaker and drbd with sl linux 6.5/6.6. all are fine.
>
> now I am tesing sl linux 7.0 and I notice when I want to promote
> the drbd resource with "pcs resource meta my-ms-drbd master-max=2".
>
>sometimes pengine fi
> On 28 Feb 2015, at 6:00 am, Покотиленко Костик wrote:
>
> В Чтв, 22/01/2015 в 14:59 +1100, Andrew Beekhof пишет:
>>> On 15 Jan 2015, at 12:54 am, Покотиленко Костик wrote:
>>>
>>> В Вто, 06/01/2015 в 16:27 +1100, Andrew Beekhof пишет:
> On 20 Dec 2014, at 6:21 am, Покотиленко Костик
>>
> On 11 Mar 2015, at 2:21 am, Dmitry Koterov wrote:
>
> On Tue, Feb 24, 2015 at 2:07 AM, Andrew Beekhof wrote:
>
> > I have a 3-node cluster where node1 and node2 are running
> > corosync+pacemaker and node3 is running corosync only (for quorum).
> > Corosync 2.3.3, pacemaker 1.1.10. Everyth
