On Fri, Oct 30, 2009 at 7:06 PM, Lars Marowsky-Bree wrote:
> On 2009-10-30T16:41:34, Andrew Beekhof wrote:
>
>> >> This does not make any sense. Sorry, let me try again.
>> >>
>> >> res1 start = set attribute
>> >> res1 stop = delete attribute
>> >>
>> >> rule for res2 with -inf score if attribut
Am Freitag, 30. Oktober 2009 18:06:56 schrieb Lars Marowsky-Bree:
> On 2009-10-30T16:41:34, Andrew Beekhof wrote:
> > >> This does not make any sense. Sorry, let me try again.
> > >>
> > >> res1 start = set attribute
> > >> res1 stop = delete attribute
> > >>
> > >> rule for res2 with -inf score i
On 2009-10-30T16:41:34, Andrew Beekhof wrote:
> >> This does not make any sense. Sorry, let me try again.
> >>
> >> res1 start = set attribute
> >> res1 stop = delete attribute
> >>
> >> rule for res2 with -inf score if attribute is set.
> >
> > better, just give all your nodes an attribute with
On Fri, Oct 30, 2009 at 4:36 PM, Andrew Beekhof wrote:
> On Fri, Oct 30, 2009 at 2:40 PM, Dominik Klein wrote:
>>> Maybe set a cluster-wide attribute, which, when set, does not allow res2
>>> to run. Ie rule with score -infinity.
>>>
>>> res1 could remove this attribute while starting and set thi
On Fri, Oct 30, 2009 at 2:40 PM, Dominik Klein wrote:
>> Maybe set a cluster-wide attribute, which, when set, does not allow res2
>> to run. Ie rule with score -infinity.
>>
>> res1 could remove this attribute while starting and set this attribute
>> when stopping.
>
> This does not make any sense
Am Freitag, 30. Oktober 2009 13:37:36 schrieb Dominik Klein:
> Michael Schwartzkopff wrote:
> > Am Freitag, 30. Oktober 2009 13:26:35 schrieb Lars Marowsky-Bree:
> >> On 2009-10-30T13:19:52, Michael Schwartzkopff wrote:
> >>> I have a three node cluster. I have two resources that are not allowed
>
> Maybe set a cluster-wide attribute, which, when set, does not allow res2
> to run. Ie rule with score -infinity.
>
> res1 could remove this attribute while starting and set this attribute
> when stopping.
This does not make any sense. Sorry, let me try again.
res1 start = set attribute
res1 st
Michael Schwartzkopff wrote:
> Am Freitag, 30. Oktober 2009 13:26:35 schrieb Lars Marowsky-Bree:
>> On 2009-10-30T13:19:52, Michael Schwartzkopff wrote:
>>> I have a three node cluster. I have two resources that are not allowed to
>>> run together in the cluster. Basically resource2 is a failover
Am Freitag, 30. Oktober 2009 13:26:35 schrieb Lars Marowsky-Bree:
> On 2009-10-30T13:19:52, Michael Schwartzkopff wrote:
> > I have a three node cluster. I have two resources that are not allowed to
> > run together in the cluster. Basically resource2 is a failover case for
> > resource1.
> >
> >
On 2009-10-30T13:19:52, Michael Schwartzkopff wrote:
> I have a three node cluster. I have two resources that are not allowed to run
> together in the cluster. Basically resource2 is a failover case for resource1.
>
> How can I tell the cluster not to run res1 and res2 together in the cluster?
Hi,
I have a three node cluster. I have two resources that are not allowed to run
together in the cluster. Basically resource2 is a failover case for resource1.
How can I tell the cluster not to run res1 and res2 together in the cluster?
Thanks.
--
Dr. Michael Schwartzkopff
MultiNET Services
11 matches
Mail list logo