On 2020-04-18 2:48 a.m., Strahil Nikolov wrote:
> On April 18, 2020 8:43:51 AM GMT+03:00, Digimer wrote:
>> For what it's worth; A lot of HA specialists spent a lot of time trying
>> to find the simplest _reliable_ way to do multi-site/geo-replicated HA.
>> I am certain you'll find a simpler
On April 18, 2020 8:43:51 AM GMT+03:00, Digimer wrote:
>For what it's worth; A lot of HA specialists spent a lot of time trying
>to find the simplest _reliable_ way to do multi-site/geo-replicated HA.
>I am certain you'll find a simpler solution, but I would also wager
>that
>when it counts, it's
For what it's worth; A lot of HA specialists spent a lot of time trying
to find the simplest _reliable_ way to do multi-site/geo-replicated HA.
I am certain you'll find a simpler solution, but I would also wager that
when it counts, it's going to let you down.
The only way to make things simpler
We only have 1 cluster per site so adding additional hardware is not optimal. I feel like I'm trying to use a saw where an axe would be the proper tool. I thank you or your time, but it appears that it may be best for me to write something from scratch for the monitoring and controlling of the
On 2020-04-17 3:20 p.m., Daniel Smith wrote:
> Thank you digimer, and I apologize for getting the wrong email.
>
>
>
> Booth was the piece I was missing. Have been researching setting that
> up and finding a third location for quorum. From what I have found, I
> believe I will need to setup
Thank you digimer, and I apologize for getting the wrong email.
Booth was the piece I was missing. Have been researching setting that up and
finding a third location for quorum. From what I have found, I believe I will
need to setup single node pacemaker clusters at each datacenter to use with
Hi Daniel,
You sent this to clusterlabs owners, instead of users. I've
changed the CC to send it to the list for a larger discussion.
The biggest problem with stretch clustering is knowing the
difference between a link fault and a site loss. Pacemaker Booth
