On 19.11.2021 20:45, Ken Gaillot wrote:
> On Fri, 2021-11-19 at 10:40 -0500, john tillman wrote:
>
>
>
>>> If pacemaker tries to stop resources due to out of quorum
>>> condition, you
>>> could set suitable failure-timeout; this will be equivalent to
>>> using "pcs
>>> resource refresh". Keep in
On 19.11.2021 19:26, john tillman wrote:
...
>>>
>>> If pacemaker tries to stop resources due to out of quorum condition, you
>>> could set suitable failure-timeout; this will be equivalent to using
>>> "pcs
>>> resource refresh". Keep in mind that pacemaker only checks for
>>> failure-timeout expi
On Fri, 2021-11-19 at 14:57 -0500, john tillman wrote:
> > On Fri, 2021-11-19 at 10:40 -0500, john tillman wrote:
> >
> >
> >
> > > > If pacemaker tries to stop resources due to out of quorum
> > > > condition, you
> > > > could set suitable failure-timeout; this will be equivalent to
> > > > us
> On Fri, 2021-11-19 at 10:40 -0500, john tillman wrote:
>
>
>
>> > If pacemaker tries to stop resources due to out of quorum
>> > condition, you
>> > could set suitable failure-timeout; this will be equivalent to
>> > using "pcs
>> > resource refresh". Keep in mind that pacemaker only checks for
> On Fri, Nov 19, 2021 at 11:26:01AM -0500, john tillman wrote:
>> Anyone have any other ideas for a configuration setting that will
>> effectively do whatever 'pcs resource refresh' is doing when quorum is
>> restored?
>
> Since you have three nodes you may want to use the third node as QDevice
>
On Fri, Nov 19, 2021 at 11:26:01AM -0500, john tillman wrote:
> Anyone have any other ideas for a configuration setting that will
> effectively do whatever 'pcs resource refresh' is doing when quorum is
> restored?
Since you have three nodes you may want to use the third node as QDevice
instead:
On Fri, 2021-11-19 at 10:40 -0500, john tillman wrote:
> > If pacemaker tries to stop resources due to out of quorum
> > condition, you
> > could set suitable failure-timeout; this will be equivalent to
> > using "pcs
> > resource refresh". Keep in mind that pacemaker only checks for
> > failure
>> On 19.11.2021 17:36, john tillman wrote:
On 18.11.2021 22:33, john tillman wrote:
>
> Greetings all,
>
> preamble: RHEL8, PCS 0.10.8, COROSYNC 3.1.0, PACEMAKER 2.0.5
>
> I have a mysql resource, cloned, that is behaving the way I wanted.
> When
> the node it
> On 19.11.2021 17:36, john tillman wrote:
>>> On 18.11.2021 22:33, john tillman wrote:
Greetings all,
preamble: RHEL8, PCS 0.10.8, COROSYNC 3.1.0, PACEMAKER 2.0.5
I have a mysql resource, cloned, that is behaving the way I wanted.
When
the node it is on is u
On 19.11.2021 17:36, john tillman wrote:
>> On 18.11.2021 22:33, john tillman wrote:
>>>
>>> Greetings all,
>>>
>>> preamble: RHEL8, PCS 0.10.8, COROSYNC 3.1.0, PACEMAKER 2.0.5
>>>
>>> I have a mysql resource, cloned, that is behaving the way I wanted.
>>> When
>>> the node it is on is unplugged fr
> On 18.11.2021 22:33, john tillman wrote:
>>
>> Greetings all,
>>
>> preamble: RHEL8, PCS 0.10.8, COROSYNC 3.1.0, PACEMAKER 2.0.5
>>
>> I have a mysql resource, cloned, that is behaving the way I wanted.
>> When
>> the node it is on is unplugged from the network quorum is lost and the
>> mysqld se
> On Thu, Nov 18, 2021 at 03:42:48PM -0500, john tillman wrote:
>> I don't believe I can since I do not have a fencing device available.
>
> As this page explains, fencing is required for the cluster to behave
> correctly:
>
> https://www.alteeve.com/w/The_2-Node_Myth
>
> Can you share what kind
12 matches
Mail list logo
