On 2014-03-14T15:50:18, David Vossel <[email protected]> wrote:
> in-flight operations always have to complete before we can process a new
> transition. The only way we can transition earlier is by killing the
> in-flight process, which results in failure recovery and possibly fencing
> depending on what operation it is.
>
> There's really nothing that can be done to speed this up except work on
> lowering the startup time of that resource.
We keep getting similar requests though - some services take a long
time, and during that interval, the cluster is essentially stuck. As the
density of resources in the cluster increases and the number of nodes
goes up, this becomes more of an issue.
It *would* be possible with changes to the TE/PE - assume in-flight
operations will complete as planned, so that any further changes to
in-flight resources would be ordered after them, the ability to accept
actions completing from previous transitions -, but it's also
non-trivial.
Pacemaker 2.0 material? ;-)
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
