On 21/08/19 14:48 +0200, Jan Pokorný wrote:
> On 20/08/19 20:55 +0200, Jan Pokorný wrote:
>> On 15/08/19 17:03 +, Michael Powell wrote:
>>> First, thanks to all for their responses. With your help, I'm
>>> steadily gaining competence WRT HA, albeit slowly.
>>>
>>> I've basically followed
On 20/08/19 20:55 +0200, Jan Pokorný wrote:
> On 15/08/19 17:03 +, Michael Powell wrote:
>> First, thanks to all for their responses. With your help, I'm
>> steadily gaining competence WRT HA, albeit slowly.
>>
>> I've basically followed Harvey's workaround suggestion, and the
>> failover I
On 21/08/19 14:49 +0530, Rohit Saini wrote:
> I am using booth (two clusters) using manual ticket. Is there any
> way for cluster-1 to know if peer cluster-2 booth-ip is not
> reachable. Here I am looking to know if there both the sites are
> connected and reachable via each other's booth-ip.
Hi ,
I am using booth (two clusters) using manual ticket. Is there any way for
cluster-1 to know if peer cluster-2 booth-ip is not reachable. Here I am
looking to know if there both the sites are connected and reachable via
each other's booth-ip.
pcs alerts gives notification about cluster
All,
We are pleased to announce the general availability of kronosnet v1.11
kronosnet (or knet for short) is the new underlying network protocol for
Linux HA components (corosync), that features the ability to use
multiple links between nodes, active/active and active/passive link
failover
