[ClusterLabs] Antw: CRM location specification and errors
andrew at beekhof.net
Mon Aug 3 21:51:13 EDT 2015
> On 26 Jun 2015, at 6:55 pm, Kristoffer Grönlund <kgronlund at suse.com> wrote:
> Andrei Borzenkov <arvidjaar at gmail.com> writes:
>> В Fri, 26 Jun 2015 10:12:00 +0200
>> Kristoffer Grönlund <kgronlund at suse.com> пишет:
>>> Andrei Borzenkov <arvidjaar at gmail.com> writes:
>>>> В Fri, 26 Jun 2015 08:28:14 +0200
>>>> "Ulrich Windl" <Ulrich.Windl at rz.uni-regensburg.de> пишет:
>>>>> I guess the cluster is running monitor operations on the forbidden node to make sure no resources run there: Meaning: If you had started those resources on the forbidden node, the cluster would stop them. To find out it runs the monitors.
>>>> Unfortunately it does not. And that was quite a nasty surprise for me
>>>> when I started to use pacemaker. It does run monitor only once (probe)
>>>> on initial startup. So no, in pacemaker there is no protection against
>>>> accident manual starting of resources that I am aware of.
>>> Just as with normal monitor operations, you have to configure it if you
>>> want it. Pacemaker doesn't monitor resources on any nodes unless
>>> configured to do so.
>>> op monitor role=Stopped
>> I do not see "role" mentioned anywhere on this page:
>> How does it look like in CIB?
> I'll avoid suggesting that the documentation needs to be updated since I
> risk having to do it myself ;)
> You can see an example of what it looks like in the CIB in this test
> // Kristoffer Grönlund
> // kgronlund at suse.com
> Users mailing list: Users at clusterlabs.org
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
More information about the Users