Re: [ClusterLabs] When the active node enters the standby state, what should be done to make the VIP not automatically jump
Hi,
My suggestion would be to unmanage the IP resource before putting the
node in standby. When a resource is unmanaged, the cluster will not
start or stop it.
On Thu, 2020-04-16 at 17:57 +0800, 邴洪涛 wrote:
> >hi:
> > We now get a strange requirement. When the active node enters
> standby
> >mode, virtual_ip will not automatically jump to the normal node, but
> >requires manual operation to achieve the jump of virtual_ip
> > The mode we use is Active / Passive mode
> > The Resource Agent we use is ocf: heartbeat: IPaddr2
> > Hope you can solve my confusion
>
> Hello,
>
> Can you provide the version of the stack, your config and the command
> you run to put the node in sandby ?
>
> Best Regards,
> Strahil Nikolov
> -
> Sorry, I don't know how to reply correctly, so I pasted the previous
> chat content on it
> The following are the commands we use
> pcs property set stonith-enabled=false
> pcs property set no-quorum-policy=ignore
> pcs resource create virtual_ip ocf:heartbeat:IPaddr2
> ip=${VIP} cidr_netmask=32 op monitor interval="10s"
>
> pcs resource create docker systemd:docker op monitor
> interval="10s" timeout="15s" op start interval="0" timeout="1200s" op
> stop interval="0" timeout="1200s"
> pcs constraint colocation add docker virtual_ip INFINITY
> pcs constraint order virtual_ip then docker
> pcs constraint location docker prefers ${MASTER_NAME}=50
>
> pcs resource create lsyncd systemd:lsyncd op monitor
> interval="10s" timeout="15s" op start interval="0" timeout="120s" op
> stop interval="0" timeout="60s"
> pcs constraint colocation add lsyncd virtual_ip INFINITY
>
> The version we use is
> Pacemaker 1.1.20-5.el7_7.2
> Written by Andrew Beekhof
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] When the active node enters the standby state, what should be done to make the VIP not automatically jump
On April 16, 2020 12:57:05 PM GMT+03:00, "邴洪涛" <695097494p...@gmail.com> wrote:
>>*hi:
>*>* We now get a strange requirement. When the active node enters
>standby
>*>*mode, virtual_ip will not automatically jump to the normal node, but
>*>*requires manual operation to achieve the jump of virtual_ip
>*>* The mode we use is Active / Passive mode
>*>* The Resource Agent we use is ocf: heartbeat: IPaddr2
>*>* Hope you can solve my confusion
>*
>Hello,
>
>Can you provide the version of the stack, your config and the command
>you run to put the node in sandby ?
>
>Best Regards,
>Strahil Nikolov
>
>-
>
>Sorry, I don't know how to reply correctly, so I pasted the previous
>chat content on it
>
>The following are the commands we use
>
>pcs property set stonith-enabled=false
>
>pcs property set no-quorum-policy=ignore
>pcs resource create virtual_ip ocf:heartbeat:IPaddr2 ip=${VIP}
>cidr_netmask=32 op monitor interval="10s"
>
>pcs resource create docker systemd:docker op monitor interval="10s"
>timeout="15s" op start interval="0" timeout="1200s" op stop
>interval="0"
>timeout="1200s"
>pcs constraint colocation add docker virtual_ip INFINITY
>pcs constraint order virtual_ip then docker
>pcs constraint location docker prefers ${MASTER_NAME}=50
>
>pcs resource create lsyncd systemd:lsyncd op monitor interval="10s"
>timeout="15s" op start interval="0" timeout="120s" op stop interval="0"
>timeout="60s"
>pcs constraint colocation add lsyncd virtual_ip INFINITY
>
>The version we use is
> Pacemaker 1.1.20-5.el7_7.2
> Written by Andrew Beekhof
If you need to enter a node in standby mode and still keep the IP on that node
- I don't think that you can do it at all.
Best Regards,
Strahil Nikolov
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] When the active node enters the standby state, what should be done to make the VIP not automatically jump
>*hi:
*>* We now get a strange requirement. When the active node enters standby
*>*mode, virtual_ip will not automatically jump to the normal node, but
*>*requires manual operation to achieve the jump of virtual_ip
*>* The mode we use is Active / Passive mode
*>* The Resource Agent we use is ocf: heartbeat: IPaddr2
*>* Hope you can solve my confusion
*
Hello,
Can you provide the version of the stack, your config and the command
you run to put the node in sandby ?
Best Regards,
Strahil Nikolov
-
Sorry, I don't know how to reply correctly, so I pasted the previous
chat content on it
The following are the commands we use
pcs property set stonith-enabled=false
pcs property set no-quorum-policy=ignore
pcs resource create virtual_ip ocf:heartbeat:IPaddr2 ip=${VIP}
cidr_netmask=32 op monitor interval="10s"
pcs resource create docker systemd:docker op monitor interval="10s"
timeout="15s" op start interval="0" timeout="1200s" op stop interval="0"
timeout="1200s"
pcs constraint colocation add docker virtual_ip INFINITY
pcs constraint order virtual_ip then docker
pcs constraint location docker prefers ${MASTER_NAME}=50
pcs resource create lsyncd systemd:lsyncd op monitor interval="10s"
timeout="15s" op start interval="0" timeout="120s" op stop interval="0"
timeout="60s"
pcs constraint colocation add lsyncd virtual_ip INFINITY
The version we use is
Pacemaker 1.1.20-5.el7_7.2
Written by Andrew Beekhof
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] When the active node enters the standby state, what should be done to make the VIP not automatically jump
hi: We now get a strange requirement. When the active node enters standby mode, virtual_ip will not automatically jump to the normal node, but requires manual operation to achieve the jump of virtual_ip The mode we use is Active / Passive mode The Resource Agent we use is ocf: heartbeat: IPaddr2 Hope you can solve my confusion ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] When the active node enters the standby state, what should be done to make the VIP not automatically jump
On April 15, 2020 2:28:33 PM GMT+03:00, "邴洪涛" <695097494p...@gmail.com> wrote: >hi: > We now get a strange requirement. When the active node enters standby >mode, virtual_ip will not automatically jump to the normal node, but >requires manual operation to achieve the jump of virtual_ip > The mode we use is Active / Passive mode > The Resource Agent we use is ocf: heartbeat: IPaddr2 > Hope you can solve my confusion Hello, Can you provide the version of the stack, your config and the command you run to put the node in sandby ? Best Regards, Strahil Nikolov ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] When the active node enters the standby state, what should be done to make the VIP not automatically jump
hi: We now get a strange requirement. When the active node enters standby mode, virtual_ip will not automatically jump to the normal node, but requires manual operation to achieve the jump of virtual_ip The mode we use is Active / Passive mode The Resource Agent we use is ocf: heartbeat: IPaddr2 Hope you can solve my confusion ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
