This must harken back to the days of yore when corrupt persistent
databases were an issue. We haven't seen this used. If CTDB fails to
start due to a corrupt persistent database then this database can be
removed by hand.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
maybe_set "--no-lmaster" "$CTDB_CAPABILITY_LMASTER" "no"
maybe_set "--nosetsched" "$CTDB_NOSETSCHED" "yes"
maybe_set "--script-log-level" "$CTDB_SCRIPT_LOG_LEVEL"
- maybe_set "--max-persistent-check-errors" "$CTDB_MAX_PERSISTENT_CHECK_ERRORS"
}
export_debug_variables ()
_dir="${CTDB_DBDIR_PERSISTENT:-${CTDB_VARDIR}/persistent}"
[ -d "$_dir" ] || return 0
- [ "${CTDB_MAX_PERSISTENT_CHECK_ERRORS:-0}" = "0" ] || return 0
-
for _db in "$_dir/"*.tdb.*[0-9] ; do
[ -r "$_db" ] || continue
check_tdb "$_db" || \
</listitem>
</varlistentry>
- <varlistentry>
- <term>CTDB_MAX_PERSISTENT_CHECK_ERRORS=<parameter>NUM</parameter></term>
- <listitem>
- <para>
- Default 0. Corresponds to
- <option>--max-persistent-check-errors</option>.
- </para>
- </listitem>
- </varlistentry>
-
<varlistentry>
<term>CTDB_NODE_ADDRESS=<parameter>IPADDR</parameter></term>
<listitem>