On Tue, 10 Apr 2018 11:24:04 +0200
Klaus Wenninger wrote:
> On 04/10/2018 08:48 AM, Jehan-Guillaume de Rorthais wrote:
> > On Mon, 09 Apr 2018 17:59:26 -0500
> > Ken Gaillot wrote:
> >
> >> On Tue, 2018-04-10 at 00:02 +0200, Jehan-Guillaume de
On 04/10/2018 08:48 AM, Jehan-Guillaume de Rorthais wrote:
> On Mon, 09 Apr 2018 17:59:26 -0500
> Ken Gaillot wrote:
>
>> On Tue, 2018-04-10 at 00:02 +0200, Jehan-Guillaume de Rorthais wrote:
>>> On Tue, 03 Apr 2018 17:35:43 -0500
>>> Ken Gaillot wrote:
On Mon, 09 Apr 2018 17:59:26 -0500
Ken Gaillot wrote:
> On Tue, 2018-04-10 at 00:02 +0200, Jehan-Guillaume de Rorthais wrote:
> > On Tue, 03 Apr 2018 17:35:43 -0500
> > Ken Gaillot wrote:
> >
> > > On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger
On Tue, 2018-04-10 at 00:02 +0200, Jehan-Guillaume de Rorthais wrote:
> On Tue, 03 Apr 2018 17:35:43 -0500
> Ken Gaillot wrote:
>
> > On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote:
> > > On 04/03/2018 05:43 PM, Ken Gaillot wrote:
> > > > On Tue, 2018-04-03 at
On Tue, 03 Apr 2018 16:59:21 -0500
Ken Gaillot wrote:
> On Tue, 2018-04-03 at 21:33 +0200, Jehan-Guillaume de Rorthais wrote:
[...]
> > > > I'm not sure to understand the doc correctly in regard with this
> > > > property. Does
> > > > pcmk_delay_max delay the request itself
On Tue, 03 Apr 2018 17:35:43 -0500
Ken Gaillot wrote:
> On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote:
> > On 04/03/2018 05:43 PM, Ken Gaillot wrote:
> > > On Tue, 2018-04-03 at 07:36 +0200, Klaus Wenninger wrote:
> > > > On 04/02/2018 04:02 PM, Ken Gaillot
On 04/05/2018 06:45 AM, Andrei Borzenkov wrote:
> 04.04.2018 01:35, Ken Gaillot пишет:
>> On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote:
> ...
> -inf constraints like that should effectively prevent
> stonith-actions from being executed on that nodes.
It shouldn't ...
04.04.2018 01:35, Ken Gaillot пишет:
> On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote:
...
>>
-inf constraints like that should effectively prevent
stonith-actions from being executed on that nodes.
>>>
>>> It shouldn't ...
>>>
>>> Pacemaker respects
On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote:
> On 04/03/2018 05:43 PM, Ken Gaillot wrote:
> > On Tue, 2018-04-03 at 07:36 +0200, Klaus Wenninger wrote:
> > > On 04/02/2018 04:02 PM, Ken Gaillot wrote:
> > > > On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais
> > > >
On Tue, 2018-04-03 at 21:33 +0200, Jehan-Guillaume de Rorthais wrote:
> On Mon, 02 Apr 2018 09:02:24 -0500
> Ken Gaillot wrote:
> > On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Sun, 1 Apr 2018 09:01:15 +0300
> > > Andrei Borzenkov
On Tue, 3 Apr 2018 07:36:31 +0200
Klaus Wenninger wrote:
> On 04/02/2018 04:02 PM, Ken Gaillot wrote:
> > On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais wrote:
> >> On Sun, 1 Apr 2018 09:01:15 +0300
> >> Andrei Borzenkov wrote:
> >>
On 04/03/2018 05:43 PM, Ken Gaillot wrote:
> On Tue, 2018-04-03 at 07:36 +0200, Klaus Wenninger wrote:
>> On 04/02/2018 04:02 PM, Ken Gaillot wrote:
>>> On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais
>>> wrote:
On Sun, 1 Apr 2018 09:01:15 +0300
Andrei Borzenkov
On Mon, 02 Apr 2018 09:02:24 -0500
Ken Gaillot wrote:
> On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais wrote:
> > On Sun, 1 Apr 2018 09:01:15 +0300
> > Andrei Borzenkov wrote:
[...]
> > > In two-node cluster you can set pcmk_delay_max so
On Tue, 2018-04-03 at 07:36 +0200, Klaus Wenninger wrote:
> On 04/02/2018 04:02 PM, Ken Gaillot wrote:
> > On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Sun, 1 Apr 2018 09:01:15 +0300
> > > Andrei Borzenkov wrote:
> > >
> > > > 31.03.2018
On 04/02/2018 04:02 PM, Ken Gaillot wrote:
> On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais wrote:
>> On Sun, 1 Apr 2018 09:01:15 +0300
>> Andrei Borzenkov wrote:
>>
>>> 31.03.2018 23:29, Jehan-Guillaume de Rorthais пишет:
Hi all,
I experienced
On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais wrote:
> On Sun, 1 Apr 2018 09:01:15 +0300
> Andrei Borzenkov wrote:
>
> > 31.03.2018 23:29, Jehan-Guillaume de Rorthais пишет:
> > > Hi all,
> > >
> > > I experienced a problem in a two node cluster. It has one
On Sun, 1 Apr 2018 09:01:15 +0300
Andrei Borzenkov wrote:
> 31.03.2018 23:29, Jehan-Guillaume de Rorthais пишет:
> > Hi all,
> >
> > I experienced a problem in a two node cluster. It has one FA per node and
> > location constraints to avoid the node each of them are
31.03.2018 23:29, Jehan-Guillaume de Rorthais пишет:
> Hi all,
>
> I experienced a problem in a two node cluster. It has one FA per node and
> location constraints to avoid the node each of them are supposed to interrupt.
>
If you mean stonith resource - for all I know location it does not
Hi all,
I experienced a problem in a two node cluster. It has one FA per node and
location constraints to avoid the node each of them are supposed to interrupt.
During some tests, a ms resource raised an error during the stop action on
both nodes. So both nodes were supposed to be fenced.
The
19 matches
Mail list logo