Thanks for the reply. I am now collocating resources but the same problem of
the resource not getting started when manually stopped persists when my
migration_threshold=2, and its the 1st time, I have brought down the
resource after doing the cleanup as well as waiting for the failure-timeout
on that node.
Disclaimer: I am also new and have not used migration-threshold yet.
But I am not sure what you mean by "manually stopped". Do you mean by
issuing a manual command "resource stop" at the crm shell? If so, the
resource will remain stopped until you issue a new start command.
If you stop the resource outside the control of pacemaker (e.g. by
killing the service) I would also expect that the resource manager would
try to restart it after monitor interval + timeout seconds.
Looking at your config I am a bit confused that there are so many lines
starting with "meta". Also there are duplicated entries of
target-role="Started". I would suggest to collect all meta attributes
after _one_ meta keyword per resource.
Additionally, at least when editing the configuration to move resources
into groups you should remove remaining "target-role" entries from the
resources themselves.
Regards,
Sven
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
