From 73ab0f991154c2651ebe737c9d9d093eaf65c652 Mon Sep 17 00:00:00 2001 From: Amitay Isaacs Date: Mon, 7 Mar 2016 18:02:02 +1100 Subject: [PATCH] ctdb-tunables: Mark tunable MaxRedirectCount obsolete Signed-off-by: Amitay Isaacs Reviewed-by: Martin Schwenke --- ctdb/doc/ctdb-tunables.7.xml | 19 ------------------- ctdb/server/ctdb_tunables.c | 2 +- 2 files changed, 1 insertion(+), 20 deletions(-) diff --git a/ctdb/doc/ctdb-tunables.7.xml b/ctdb/doc/ctdb-tunables.7.xml index a6ef4353545..38f0069f054 100644 --- a/ctdb/doc/ctdb-tunables.7.xml +++ b/ctdb/doc/ctdb-tunables.7.xml @@ -281,25 +281,6 @@ - - MaxRedirectCount - Default: 3 - - If we are not the DMASTER and need to fetch a record across the - network we first send the request to the LMASTER after which the - record is passed onto the current DMASTER. If the DMASTER changes - before the request has reached that node, the request will be - passed onto the "next" DMASTER. For very hot records that migrate - rapidly across the cluster this can cause a request to "chase" - the record for many hops before it catches up with the record. - - - When chasing a record, this is how many hops we will chase - the record for before going back to the LMASTER to ask for - new guidance. - - - MonitorInterval Default: 15 diff --git a/ctdb/server/ctdb_tunables.c b/ctdb/server/ctdb_tunables.c index 0cc7be3ad06..db130d0152e 100644 --- a/ctdb/server/ctdb_tunables.c +++ b/ctdb/server/ctdb_tunables.c @@ -35,7 +35,7 @@ static const struct { size_t offset; bool obsolete; } tunable_map[] = { - { "MaxRedirectCount", 3, offsetof(struct ctdb_tunable_list, max_redirect_count), false }, + { "MaxRedirectCount", 3, offsetof(struct ctdb_tunable_list, max_redirect_count), true }, { "SeqnumInterval", 1000, offsetof(struct ctdb_tunable_list, seqnum_interval), false }, { "ControlTimeout", 60, offsetof(struct ctdb_tunable_list, control_timeout), false }, { "TraverseTimeout", 20, offsetof(struct ctdb_tunable_list, traverse_timeout), false },