[Pacemaker] pacemaker and the clone resource

Andrew Beekhof beekhof at gmail.com
Tue Apr 1 14:40:04 EDT 2008


On Apr 1, 2008, at 8:00 PM, Lars Marowsky-Bree wrote:

> On 2008-04-01T18:40:12, Andrew Beekhof <beekhof at gmail.com> wrote:
>
>> On Tue, Apr 1, 2008 at 3:44 PM, Hartje Bruns <hb at bos-bremen.de>  
>> wrote:
>>>
>>> Hi,
>>> i started testing the clone resource (on a two node cluster one  
>>> tomcat
>>> running on each). I want to be able to shutdown just one tomcat (=  
>>> one clone
>>> instance). Trying that with hb_gui results in shutting down both  
>>> instances.
>>>
>>> Does anyone know if that is a feature or a bug ;-)
>>
>> Feature IIRC
>
> Yes, the GUI applies the target role to the container or the primitive
> directly.
>
>
>> You have two options,
>> - if you don't care which one is shut down, then set clone_max=1
>
> ... can be done via the GUI.
>
>> - otherwise, use a rsc_location constraint to prevent the clone from
>> running on that node
>
> That probably works using the migrate button?

depends how the gui implements it (ie. if it also adds the -INFINITY  
constraint) 




More information about the Pacemaker mailing list