On 2010/11/09 7:07 PM, Vladimir Legeza wrote:
The only solution I know, is to change "/clone-node-max/" param on the fly.
See
http://oss.clusterlabs.org/pipermail/pacemaker/2010-November/008148.html
for details.
I have read the thread - it is a slightly different problem. In your
case, it is possible that setting resource-stickiness=0 for the
resources, and clone-node-max to 4 or 8, will solve your problem, which
is to allow the resources to fail back to the nodes they were running on
originally.
In my case, setting clone-node-max=1 will work, until a node fails, in
which case I would have to change it again. I would rather not have to
change cluster parametersin this manner.
Is there a way to request pacemaker to try split the clones up if
possible over the available nodes?
Regards
Chris
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
