On April 8, 2020 8:32:59 PM GMT+03:00, Sherrard Burton
wrote:
>
>
>On 4/8/20 1:09 PM, Andrei Borzenkov wrote:
>> 08.04.2020 10:12, Jan Friesse пишет:
>>> Sherrard,
>>>
i could not determine which of these sub-threads to include this
>in,
so i am going to (reluctantly) top-post it.
> Yeah, because there is no such logic in the scripts.
can this somehow be implemented?
> Also when using multipath - your clients should not realize that a restart
> has occured.
thats true, but lsat time it doesn't work, and I've absolutly no glue why it
fails last time.
I can't play with
On 4/8/20 1:09 PM, Andrei Borzenkov wrote:
08.04.2020 10:12, Jan Friesse пишет:
Sherrard,
i could not determine which of these sub-threads to include this in,
so i am going to (reluctantly) top-post it.
i switched the transport to udp, and in limited testing i seem to not
be hitting the
08.04.2020 10:12, Jan Friesse пишет:
> Sherrard,
>
>> i could not determine which of these sub-threads to include this in,
>> so i am going to (reluctantly) top-post it.
>>
>> i switched the transport to udp, and in limited testing i seem to not
>> be hitting the race condition. of course i have
On Wed, 8 Apr 2020 08:07:54 -0400
Sherrard Burton wrote:
> On 4/8/20 3:09 AM, Ulrich Windl wrote:
> Jehan-Guillaume de Rorthais schrieb am 07.04.2020 um
> 23:02 in
> > Nachricht
> > <20140_1586293370_5E8CEA7A_20140_452_1_20200407230230.1bc9b7b0@firost>:
> >> On Tue, 7 Apr 2020
On 4/8/20 5:13 AM, Jan Friesse wrote:
please forgive me if i have overlooked the answer somewhere.
i have an existing cluster that is already configured with a qdevice.
i now wish to update that configuration to point at a different qdevice.
background:
for the sake of working through the
On 4/8/20 3:09 AM, Ulrich Windl wrote:
Jehan-Guillaume de Rorthais schrieb am 07.04.2020 um 23:02 in
Nachricht
<20140_1586293370_5E8CEA7A_20140_452_1_20200407230230.1bc9b7b0@firost>:
On Tue, 7 Apr 2020 14:13:35 -0400
Sherrard Burton wrote:
[...]
But the best protection is to disable
please forgive me if i have overlooked the answer somewhere.
i have an existing cluster that is already configured with a qdevice. i
now wish to update that configuration to point at a different qdevice.
background:
for the sake of working through the initial configuration details,
tuning,
Sherrard,
i could not determine which of these sub-threads to include this in, so
i am going to (reluctantly) top-post it.
i switched the transport to udp, and in limited testing i seem to not be
hitting the race condition. of course i have no idea whether this will
behave consistently, or
>>> Jehan-Guillaume de Rorthais schrieb am 07.04.2020 um
>>> 23:02 in
Nachricht
<20140_1586293370_5E8CEA7A_20140_452_1_20200407230230.1bc9b7b0@firost>:
> On Tue, 7 Apr 2020 14:13:35 -0400
> Sherrard Burton wrote:
[...]
> But the best protection is to disable pacemaker on boot so an admin can
>
Sherrard,
On 4/7/20 4:09 AM, Jan Friesse wrote:
Sherrard and Andrei
On 4/6/20 4:10 PM, Andrei Borzenkov wrote:
06.04.2020 20:57, Sherrard Burton пишет:
On 4/6/20 1:20 PM, Sherrard Burton wrote:
On 4/6/20 12:35 PM, Andrei Borzenkov wrote:
06.04.2020 17:05, Sherrard Burton пишет:
On Tue, 7 Apr 2020 14:13:35 -0400
Sherrard Burton wrote:
On 4/7/20 1:16 PM, Andrei Borzenkov wrote:
07.04.2020 00:21, Sherrard Burton пишет:
It looks like some timing issue or race condition. After reboot node
manages to contact qnetd first, before connection to other node is
established.
12 matches
Mail list logo
