I'll try IPaddr2 cloning and will read the code.
Thank you, Ken.
Regards,
Takehiro
2017-06-08 1:58 GMT+09:00 Ken Gaillot :
> On 06/02/2017 06:33 AM, Takehiro Matsushima wrote:
>> Hi,
>>
>> You should not clone IPaddr2 resource.
>> Clone means that to run the resource at same time on both nodes, s
On 06/01/2017 02:44 PM, Attila Megyeri wrote:
> Ken,
>
> I noticed something strange, this might be the issue.
>
> In some cases, even the manual cleanup does not work.
>
> I have a failed action of resource "A" on node "a". DC is node "b".
>
> e.g.
> Failed actions:
> jboss_imssrv1_m
Hi,
Thanks for the info. More inline below.
* Marek Grac [20170607 04:10]:
> Hi,
>
> On Tue, Jun 6, 2017 at 3:52 PM, Jean-Francois Malouin <
> jean-francois.malo...@bic.mni.mcgill.ca> wrote:
>
> > Hi,
> >
> > Starting to configure a two-nodes cluste
On 06/02/2017 06:33 AM, Takehiro Matsushima wrote:
> Hi,
>
> You should not clone IPaddr2 resource.
> Clone means that to run the resource at same time on both nodes, so
> these nodes will have same duplicated IP address on a network.
>
> Specifically, you need to configure a IPaddr2 resource run
On 05/30/2017 11:47 AM, Przemyslaw Kulczycki wrote:
> Hi.
> I'm trying to setup a 2-node corosync+pacemaker cluster to function as
> an active-active setup for nginx with a shared IP.
>
> I've discovered (much to my disappointment) that every time I restart
> one node or put it in standby, the sec
On 06/05/2017 10:19 AM, iva...@libero.it wrote:
> Hello,
> could you explain the meaning of fields in "crm_resource -c" command (c
> in lowercase)?
>
> I've tried to search on web but i didn't find anything.
>
> Thanks and regards
>
> Ivan
It's used solely by pacemaker's cluster test suite (CTS
Hi,
On Tue, Jun 6, 2017 at 3:52 PM, Jean-Francois Malouin <
jean-francois.malo...@bic.mni.mcgill.ca> wrote:
> Hi,
>
> Starting to configure a two-nodes cluster, runnning Debian Jessie 8.8
> Stack: corosync, pacemaker version 1.1.15-e174ec8.
>
> I'm confused with the different fencing agents relat
