Will the time server gap cause the split brain issue? if yes, what is the maximum time gap allowed?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Will the time server gap cause the split brain issue? if yes, what is the maximum time gap allowed?

DouglasJD
Will the time server gap cause the split brain issue? if yes, what is the maximum time gap allowed?
Reply | Threaded
Open this post in threaded view
|

Re: Will the time server gap cause the split brain issue? if yes, what is the maximum time gap allowed?

DouglasJD
The second attribute is "max-delay". It specifies the number of milliseconds the dispatcher waits at a maximum to check its dispatch queue. This delay avoids that the dispatcher waits too long in case the system time has been changed while the router is running, for example, due to summer / winter time changes. The default value is 10 seconds (10000 milliseconds), so the dispatcher checks its dispatch queue at least every 10 seconds for outstanding timers.

---------------------------------------------------
Does it mean it is not allowed to more than 10 seconds?
Reply | Threaded
Open this post in threaded view
|

Re: Will the time server gap cause the split brain issue? if yes, what is the maximum time gap allowed?

IIT Software
Administrator
Only if you have changed the HA Controller Swiftlet config. There are 2 attributes heart-beat-interval and heart-beat-missing-threshold which determines when the connection is considered dead and closed. The default sums up to 20 secs.

Have a look into error/warning.log of the instances. If that happened you should see that. My guess is rather that the TCP connection dropped for some other reason, e.g. TCP timeout due to the time change etc.
Reply | Threaded
Open this post in threaded view
|

Re: Will the time server gap cause the split brain issue? if yes, what is the maximum time gap allowed?

DouglasJD
We have identified the problem to cause the time gap. But I am still worry about it is not root reason to cause the split brain problem. We will keep on monitoring the log later. Meanwhile we have a TCP heartbeat application listening to another port to trace the connection as well.  Thanks a lots for your reply