Ronnie Sahlberg a3bbe238c9 The ctdb daemon keeps track of whether the recovery process is running ...

correctly by measuring how long it was since the last successful
communication with the recovery daemon was recorded.

After a certain timeout the ctdb daemon would deem the recovery daemon
as inoperable and shut down.

If the system clock is suddenly changed forward by many (60 or more)
seconds this could cause the timeout to trigger prematurely/immediately
where ctdb would incorrectly think that more than 60 seconds had passed
since last successful communications and thus abort.

Instead of cehcking for one timeout occuring, only deem the recovery
daemon to be "down" and trigger a shutdown if communications have
timedout for three intervals in a row.

(This used to be ctdb commit 196968c552e6ebcb57389d769a4b25f42fa8bc5d)

2008-09-17 14:17:41 +10:00

..

cmdline.h

moved cmdline.c to common code

2007-04-17 22:16:50 +10:00

ctdb_private.h

The ctdb daemon keeps track of whether the recovery process is running

2008-09-17 14:17:41 +10:00

ctdb.h

additional monitoring between the two daemons.

2008-09-09 13:44:46 +10:00

idtree.h

- added in idtree for efficient reqid handling

2006-11-28 20:48:34 +11:00

includes.h

track both when we last started and ended a recovery.

2008-07-02 13:55:59 +10:00