On 10/10/16 19:35, Eric Robinson wrote:
> Basically, when we turn off a switch, I want to keep the cluster from failing
> over before Linux bonding has had a chance to recover.
>
> I'm mostly interested in prventing false-positive cluster failovers that
> might occur during manual network
On 10/10/2016 08:35 PM, Eric Robinson wrote:
> Basically, when we turn off a switch, I want to keep the cluster from failing
> over before Linux bonding has had a chance to recover.
>
> I'm mostly interested in prventing false-positive cluster failovers that
> might occur during manual network
Basically, when we turn off a switch, I want to keep the cluster from failing
over before Linux bonding has had a chance to recover.
I'm mostly interested in prventing false-positive cluster failovers that might
occur during manual network maintenance (for example, testing switch and link
I'm mostly interested in prventing false-positive cluster failovers that might
occur during manual network maintenance (for example, testing switch and link
outages).
>> Thanks for the clarification. So what's the easiest way to ensure that the
>> cluster waits a
>> desired timeout before
o:ccaul...@redhat.com]
> Sent: Monday, October 10, 2016 4:34 AM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] Establishing Timeouts
>
> On 10/10/16 05:51, Eric Robinson wrote:
>> I have about a dozen corosync+pacemaker clusters and I am just now getting
>> around
On 10/10/16 05:51, Eric Robinson wrote:
> I have about a dozen corosync+pacemaker clusters and I am just now getting
> around to understanding timeouts.
>
> Most of my corosync.conf files look something like this:
>
> version:2
> token: 5000
>
I have about a dozen corosync+pacemaker clusters and I am just now getting
around to understanding timeouts.
Most of my corosync.conf files look something like this:
version:2
token: 5000
token_retransmits_before_loss_const: 10
join:
