On 2013-07-12T12:19:40, Ulrich Windl <[email protected]> wrote:
> BTW: The way "resource restart" is implemented (i.e.: stop & wait, then
> start) has a major problem: If stop causes to fence the node where the crm
> command is running, the resource will remain stopped even after the node
> restarted.
Yes. That's a limitation that's difficult to overcome. "restart" is a
multi-phase command, so if something happens to the node where it runs,
you have a problem.
But the need for a manual restart should be rare. If the resource is
running and healthy according to monitor, why should it be necessary?
;-)
(Another way to trigger a restart is to modify the instance parameters.
Set __manual_restart=1 and it'll restart.)
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
