Running ctdb with a designated master

Steve French smfrench at
Tue Jun 21 08:37:12 UTC 2016

On Tue, Jun 21, 2016 at 3:31 AM, Steve French <smfrench at> wrote:
> On Tue, Jun 21, 2016 at 3:16 AM, Steve French <smfrench at> wrote:
>> I tried some experiments with forcing only one node (a cluster file
>> system's metadata server e.g.) to be ctdb master by putting the line
>> in the ctdb config file of all other ctdb nodes, and removing the line
>> from those systems as well and specifying
>> CTDB_RECOVERY_LOCK=/var/lock/.recoverylock
>> only on the master.
>> I was wondering if it is safe to remove the CTDB_RECOVERY_LOCK file
>> from the config of the non-master nodes - it seemed to work, but there
>> are various warnings about never running without a CTDB_RECOVERY_LOCK
>> line.
> This is looking strange - I rebooted a machine as an experiment (not
> the master), and the node went unhealthy when it started back up -
> looking in the logs it tried to grab the recovery lock
> (/var/lock/.recoverylock) even though I don't have that line
> configured on that node.  It is apparently getting the location of the
> recovery lock from the master - and then won't start because it thinks
> it should be locked (it is but on the master - it shouldn't be using
> it, it is a local file, a dummy file).
> If I am forcing one node to be the master by setting recmaster = no in
> the config, should I remove CTDB_RECOVERY_LOCK from ALL nodes ctdb
> configuration?

By the way - that did seem to work ... but seems a little strange



More information about the samba-technical mailing list