After configuration changes ctdbd_wrapper will no longer see the
CTDB_RECOVERY_LOCK option. The daemon already logs a warning if the
recovery lock is not set, so simply drop this extra warning.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
ctdb_options="${ctdb_options}${ctdb_options:+ }${1}${sep}${val}"
}
- if [ -z "$CTDB_RECOVERY_LOCK" ] ; then
- echo "No recovery lock specified. Starting CTDB without split brain prevention."
- fi
- maybe_set "--reclock" "$CTDB_RECOVERY_LOCK"
-
# build up ctdb_options variable from optional parameters
+ maybe_set "--reclock" "$CTDB_RECOVERY_LOCK"
maybe_set "--logging" "$CTDB_LOGGING"
maybe_set "--listen" "$CTDB_NODE_ADDRESS"
maybe_set "--dbdir" "$CTDB_DBDIR"