> Well, that does not sound very polite to user :)
The thing that really threw me off was pacemaker rebooting the node as soon as
I'd try to start the cluster on it without the database running.
Is there a way to prevent this from happening? Some way to indicate to
Pacemaker, "Hey, I'm not wil
On Thu, 2018-05-31 at 22:43 +0200, Jehan-Guillaume de Rorthais wrote:
> On Thu, 31 May 2018 22:52:12 +0300
> Andrei Borzenkov wrote:
>
> > 31.05.2018 22:18, Jehan-Guillaume de Rorthais пишет:
> > > Sorry for getting back to you so late.
> > >
> > > On Fri, 25 May 2018 11:58:59 -0600
> > > Casey
On Thu, 31 May 2018 22:52:12 +0300
Andrei Borzenkov wrote:
> 31.05.2018 22:18, Jehan-Guillaume de Rorthais пишет:
> > Sorry for getting back to you so late.
> >
> > On Fri, 25 May 2018 11:58:59 -0600
> > Casey & Gina wrote:
> >
> >>> On May 25, 2018, at 7:01 AM, Casey Allen Shobe
> >>> wrot
31.05.2018 22:18, Jehan-Guillaume de Rorthais пишет:
> Sorry for getting back to you so late.
>
> On Fri, 25 May 2018 11:58:59 -0600
> Casey & Gina wrote:
>
>>> On May 25, 2018, at 7:01 AM, Casey Allen Shobe
>>> wrote:
Actually, why is Pacemaker fencing the standby node just because a
>>>
Sorry for getting back to you so late.
On Fri, 25 May 2018 11:58:59 -0600
Casey & Gina wrote:
> > On May 25, 2018, at 7:01 AM, Casey Allen Shobe
> > wrote:
> >> Actually, why is Pacemaker fencing the standby node just because a
> >> resource fails to start there? I thought only the master sho
> On May 25, 2018, at 7:01 AM, Casey Allen Shobe
> wrote:
>
>> Actually, why is Pacemaker fencing the standby node just because a resource
>> fails to start there? I thought only the master should be fenced if it were
>> assumed to be broken.
This is probably the most important thing to ask