02.05.2018 07:28, 范国腾 пишет:
> Andrei,
>
> We set "pcs property set no-quorum-policy=freeze;" If we want to keep
> this "freeze" value, could you please tell what quorum parameter we
> should set?
>
There is no other parameter. Either you base your cluster on quorum or
you base your cluster on
Andrei,
We set "pcs property set no-quorum-policy=freeze;" If we want to keep this
"freeze" value, could you please tell what quorum parameter we should set?
Thanks
-邮件原件-
发件人: Users [mailto:users-boun...@clusterlabs.org] 代表 Andrei Borzenkov
发送时间: 2018年5月2日 12:20
收件人:
02.05.2018 05:52, 范国腾 пишет:
> Hi,
> The cluster has three nodes: one is master and two are slave. Now we run “pcs
> cluster stop --all” to stop all of the nodes. Then we run “pcs cluster start”
> in the master node. We find it not able to started. The cause is that the
> stonith resource could
Hi,
The cluster has three nodes: one is master and two are slave. Now we run “pcs
cluster stop --all” to stop all of the nodes. Then we run “pcs cluster start”
in the master node. We find it not able to started. The cause is that the
stonith resource could not be started so all of the other
Let me first thank this community for being so active. I have learned a lot by
watching the discussions.
I have noticed that in our environment, I am seeing high rate of my RHEL 7
fence agent (fence_ipmilan) timing out on monitoring operations. We use HP iLO
3/4/5 power fencing. I have