[Pacemaker] Stop one instance in a clone

[Serge Dubrouski]

On Wed, Jun 30, 2010 at 11:07 AM, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> Hi,
>
> On Wed, Jun 30, 2010 at 10:57:21AM -0600, Serge Dubrouski wrote:
>> Hello -
>>
>> Is there any way to stop an instance of a cloned resource on a
>> particular node using crm shell?
>
> How would you stop it with crm_resource?

Actually I don't know. So let me change my question: Is there any way
to stop just one instance of a cloned resource using any of pacemaker
commands? Let say I need to do a maintenance on one of the nodes but I
don't want to completely stop corosync/heartbeat there. One solution
is to put a cloned resource into unmanaged state and then stop it
manually on a given node. But in this case I have to make sure that
all dependent resources were migrated out of that node.

Changing clone-max to clone-max - 1 and manual stopping of the
resource instance might also work.



>
> Perhaps with one -inf location constraint for the target node?
>
> Thanks,
>
> Dejan
>
>
>> --
>> Serge Dubrouski.
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at 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
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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
>



-- 
Serge Dubrouski.