On Mon, Jun 25, 2012 at 9:51 PM, David Coulson <da...@davidcoulson.net> wrote: > I've a couple of cloned resources which need to be restarted one at a time > as part of a batch process. > > If I do a 'crm -w resource restart cl-whatever', it restarts the whole lot > at once. I can do a 'service appname stop' on each box, wait for pacemaker > to notice it is down, then let it restart it and move to the next one, but > it's a difficult process establishing if pacemaker restarted it already.
what about putting 'service appname status' in a loop? there will be a way to do this generically when 1.1.8 comes out. > > Is there a crm command to restart the resource on only one node? I tried > doing 'crm -w resource restart re-whatever:0', but it told me the resource > does not exist - That works for a cleanup though. I have other resources > running on each node which I don't want restarted, so I can't put the node > in standby and bring it back online. > > I'm running Pacemaker 1.1.6-3.el6-a02c0f19a00c1eb2527ad38f146ebc0834814558 > > Thanks- > David > > _______________________________________________ > 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://bugs.clusterlabs.org _______________________________________________ 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://bugs.clusterlabs.org
