[Pacemaker] Migrate/run resource only if m/s resource is master/promoted on target node (follow-up)

[hj lee]

On Thu, Dec 31, 2009 at 3:06 AM, Martin Gombač <martin at isg.si> wrote:

>
>> First why do you set max-master=2? So both nodes are promoted and both
>> nodes are master. Then your colocation constraints does not make sense.
>> Because Hosting has to be started on both nodes. If this is not what you
>> want, then please remove max-master=2. I think the default is 1.
>>
>
> I have to have both drbd devices in primary mode (promoted), so that live
> migration works. Hopefully i can fix my collocation constraints with your
> advice, to make sense for this setup. I wish to tell resource manager that
> Hosting resource can only run, if underlying drbd device is in primary mode,
> if not, then don't bother starting or migrating resource there. I wish that
> Hosting is started only once cluster-wide.
>
> That's OK. Then the colocation constraint is no effect, please remove it.

Please do these:
-Increase log level at crmd and pengine by sending USR1 signal 3 times.
-Restart syslog to clean up the existing log.
-Post the output of crm_mon -1
-Post the output of ptest -sL
-Post the output of cat /proc/drbd

-Stop heartbeat at one of nodes

-Post the output of crm_mon -1
-Post the output of ptest -sL
-Post the output of cat /proc/drbd

-Post the /var/log/messages file

Thanks
hj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091231/e29fe532/attachment-0001.htm>