diff options
author | Tor Brede Vekterli <vekterli@verizonmedia.com> | 2019-03-08 12:58:31 +0100 |
---|---|---|
committer | Tor Brede Vekterli <vekterli@verizonmedia.com> | 2019-03-14 14:43:03 +0000 |
commit | 57b4604fc462cdc18e00bfd425a2211fac429869 (patch) | |
tree | 9797e52a497b001d89cc197b320b1deecda6b236 /configdefinitions | |
parent | 05f27f6cfcda786232fa6da47154784dce2483e1 (diff) |
Support configurable two-phase state transitions in cluster controller
Diffstat (limited to 'configdefinitions')
-rw-r--r-- | configdefinitions/src/vespa/fleetcontroller.def | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/configdefinitions/src/vespa/fleetcontroller.def b/configdefinitions/src/vespa/fleetcontroller.def index 04c9e3b7c73..62f3b6759c3 100644 --- a/configdefinitions/src/vespa/fleetcontroller.def +++ b/configdefinitions/src/vespa/fleetcontroller.def @@ -166,3 +166,15 @@ cluster_has_global_document_types bool default=false ## Bucket merges are considered complete when: ## ((buckets_total - buckets_pending) / buckets_total)) >= min_merge_completion_ratio min_merge_completion_ratio double default=1.0 + +## If enabled, cluster state transitions are performed as two distinct phases: +## +## 1) state bundle propagation and bucket info gathering phase +## 2) state activation phase, which is not performed until all nodes have completed phase 1 +## +## This is to enable read-only operations to pass through the system during phase 1 +## while nodes await phase 2. If this feature is disabled, nodes will implicitly do +## phase 2 as part of phase 1 at their own leisure, which means that actual state +## activation may happen at wildly different times throughout the cluster. The 2 phase +## transition logic aims to minimize the window of time where active states diverge. +enable_two_phase_cluster_state_transitions bool default=false |