Add configurable automatic group up/down feature based on node availability

Available under content cluster tuning tag; feature is currently disabled by
default (need prod experience for this first).
Also improves handling of nodes removed from config by ensuring these are
taken out of the core working cluster state instead of just patched away
before each state publish.

1 files changed, 6 insertions, 1 deletions

diff --git a/config-model/src/main/resources/schema/content.rnc b/config-model/src/main/resources/schema/content.rnc
index 36a8dd276ef..1c20acdc0bd 100644
--- a/config-model/src/main/resources/schema/content.rnc
+++ b/config-model/src/main/resources/schema/content.rnc
@@ -60,6 +60,10 @@ PersistenceThreads = element persistence-threads {
   Thread+
 }
 
+MinNodeRatioPerGroup = element min-node-ratio-per-group {
+  xsd:double { minInclusive = "0" maxInclusive = "1" }
+}
+
 ClusterControllerTuning = element cluster-controller {
     element init-progress-time { xsd:string { pattern = "([0-9\.]+)\s*([a-z]+)?" } }? &
     element transition-time {  xsd:string { pattern = "([0-9\.]+)\s*([a-z]+)?" }  }? &
@@ -85,7 +89,8 @@ ClusterTuning = element tuning {
    VisitorTuning? &
    ClusterControllerTuning? &
    Maintenance? &
-   PersistenceThreads?
+   PersistenceThreads? &
+   MinNodeRatioPerGroup?
 }
 
 Content = element content {