Hi!
On " First of all, there no fencing at all, it is off." Maybe the default
configuration should involve a fencing agent that sends an SMS like this to all
admins:
"Hey, get out of the bed and drive to work: nodeX has to be reset to continue
working. You get this message, because you didn't
Hi!
Just some personal comment: If an application isn't cluster-aware (has no
provisions to run in a HA environment), you may improve its uptime using a
cluster, but you cannot really make it "HA". Just consider the app needs manual
intervention after it crashed...
Kind regards,
Ulrich
From:
Hi!
I wonder: Shouldn’t node fencing step in? What do other nodes say about the
situation?
Regards,
Ulrich
From: Users On Behalf Of Klaus Wenninger
Sent: Monday, April 22, 2024 11:06 AM
To: NOLIBOS Christophe
Cc: Cluster Labs - All topics related to open-source clustering welcomed
Subject:
On Mon, 2024-05-06 at 10:05 -0500, Ken Gaillot wrote:
> On Fri, 2024-05-03 at 16:18 +0300, ale...@pavlyuts.ru wrote:
> > Hi,
> >
> > > > Thanks great for your suggestion, probably I need to think
> > > > about
> > > > this
> > > > way too, however, the project environment is not a good one to
> >
On Fri, 2024-05-03 at 16:18 +0300, ale...@pavlyuts.ru wrote:
> Hi,
>
> > > Thanks great for your suggestion, probably I need to think about
> > > this
> > > way too, however, the project environment is not a good one to
> > > rely on
> > > fencing and, moreover, we can't control the bottom layer a
On Fri, May 3, 2024 at 8:59 PM wrote:
> Hi,
>
> > > Also, I've done wireshark capture and found great mess in TCP, it
> > > seems like connection between qdevice and qnetd really stops for some
> > > time and packets won't deliver.
> >
> > Could you check UDP? I guess there is a lot of UDP packet
