mirror of
https://github.com/samba-team/samba.git
synced 2025-01-11 05:18:09 +03:00
ffe62722cb
The decision mechanism which records of a persistent db are to be pulled into the recdb during recovery is now as follows: * Usually a record with the higher rsn than that already stored is taken. (Just as for normal tdbs.) * If a transaction is running on some node, then those nodes copies of all records are taken and are not overwritten later by other nodes' copies. In order to keep track of whether a record's copy was obtained from a node with a transaction running, the recovery mechanism misuses the ctdb tdb header field 'lacount' in the recdb. It is cleared later when pushing out the recdb database to the other nodes. This way, an incomplete transaction is not spoiled when a recovery interrupts and the replay should usually succeed (possibly after a few retries). Michael (This used to be ctdb commit 8aef46d2aab3efb322dda51eaa202653cefd5222) |
||
|---|---|---|
| .. | ||
| ctdb_banning.c | ||
| ctdb_call.c | ||
| ctdb_control.c | ||
| ctdb_daemon.c | ||
| ctdb_freeze.c | ||
| ctdb_keepalive.c | ||
| ctdb_lockwait.c | ||
| ctdb_logging.c | ||
| ctdb_ltdb_server.c | ||
| ctdb_monitor.c | ||
| ctdb_persistent.c | ||
| ctdb_recover.c | ||
| ctdb_recoverd.c | ||
| ctdb_server.c | ||
| ctdb_serverids.c | ||
| ctdb_takeover.c | ||
| ctdb_traverse.c | ||
| ctdb_tunables.c | ||
| ctdb_uptime.c | ||
| ctdb_vacuum.c | ||
| ctdbd.c | ||
| eventscript.c | ||