by devops02 » Tue Aug 05, 2014 2:52 pm
Thank you for using Aerospike and welcome! As for your question to see if
there any way to get rid of this “a few seconds downtime”?
You can minimize the downtime in the configuration. To do that you will have to go into the Heartbeat Stanza and change the configuration of the Interval and the Timeout.
The Interval controls how often to send a heartbeat packet and the Timeout controls the number of intervals after which a node is considered to be missing by the rest of the nodes in the cluster if they haven’t received the heartbeat from missing node. By default they are set as:
The formula to find out how many seconds it takes for one node to discover if its missing or to send a heartbeat is by Interval x timeout. So in this case, the default is .150 (milliseconds) x 10 (number of heartbeat intervals to wait before timing out a node) = 1.5 seconds (which is fairly fast) for it to detect if a node is missing or not receiving a heartbeat. You can adjust these two factors to shorten the downtime by changing the
and see if that result meet your need.
One more thing to considered though when using cloud is the network variability. Often cloud providers network latency is not consistent over time. This can cause problems with heartbeat packet delivery times. More info can be found on our website http://www.aerospike.com/docs/operations/configure/network/heartbeat/
Hope this helps!