Re: [ClusterLabs] Cloned IP not moving back after node restart or standby

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

Re: [ClusterLabs] Cloned IP not moving back after node restart or standby

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

Re: [ClusterLabs] Cloned IP not moving back after node restart or standby

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 runs on a node which cloned nginx is running, by collocation

[ClusterLabs] Cloned IP not moving back after node restart or standby

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 second instance of the cloned IP gets moved to the first node and