[PATCH] ctdb-readonly: Do not abort if revoke of readonly record fails on a node
amitay at gmail.com
Mon Aug 11 21:37:03 MDT 2014
Revoking readonly record involves first marking the record on dmaster
as RO_REVOKING_READONLY. Then all the other nodes are sent updaterecord
control to get rid of RO_DELEGATIONS. Once that succeeds, the record
is marked RO_REVOKING_COMPLETE.
Currently, revoking of readonly delegations on the nodes is tried only
once. If a node goes in recovery, it can fail updaterecord control and
revoke code will abort ctdb. Since database recovery would revoke all
readonly delegations anyway, there is no reason to abort. Simply undo
the start of revoke process by resetting RO_REVOKIGN_READONLY flag.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4399 bytes
Desc: not available
More information about the samba-technical