This is an automated email from the ASF dual-hosted git repository.
ab pushed a commit to branch jira/solr-15300
in repository https://gitbox.apache.org/repos/asf/solr.git
The following commit(s) were added to refs/heads/jira/solr-15300 by this push:
new b3ffff4 SOLR-15300: Changed the thresholds, updated the docs.
b3ffff4 is described below
commit b3ffff450bec10e4fea4690c61b3bec8ea8f2566
Author: Andrzej Bialecki <[email protected]>
AuthorDate: Thu May 6 11:27:27 2021 +0200
SOLR-15300: Changed the thresholds, updated the docs.
---
.../org/apache/solr/handler/admin/ClusterStatus.java | 6 ++----
solr/solr-ref-guide/src/cluster-node-management.adoc | 20 ++++++++++++--------
2 files changed, 14 insertions(+), 12 deletions(-)
diff --git
a/solr/core/src/java/org/apache/solr/handler/admin/ClusterStatus.java
b/solr/core/src/java/org/apache/solr/handler/admin/ClusterStatus.java
index d75e8ba..959068c 100644
--- a/solr/core/src/java/org/apache/solr/handler/admin/ClusterStatus.java
+++ b/solr/core/src/java/org/apache/solr/handler/admin/ClusterStatus.java
@@ -59,10 +59,8 @@ public class ClusterStatus {
/** No leader or most replicas down. */
RED;
- // somewhat higher than 2/3
- public static final float ORANGE_LEVEL = 0.67f;
- // somewhat higher than 1/3
- public static final float RED_LEVEL = 0.34f;
+ public static final float ORANGE_LEVEL = 0.5f;
+ public static final float RED_LEVEL = 0.1f;
public static Health calcShardHealth(float fractionReplicasUp, boolean
hasLeader) {
if (hasLeader) {
diff --git a/solr/solr-ref-guide/src/cluster-node-management.adoc
b/solr/solr-ref-guide/src/cluster-node-management.adoc
index d187f7f..85d384b 100644
--- a/solr/solr-ref-guide/src/cluster-node-management.adoc
+++ b/solr/solr-ref-guide/src/cluster-node-management.adoc
@@ -27,14 +27,18 @@ These API commands work with a SolrCloud cluster at the
entire cluster level, or
Fetch the cluster status including collections, shards, replicas,
configuration name as well as collection aliases and cluster properties.
Additionally, this command reports a `health` status of each collection and
shard, in
-order to make it easier to monitor the operational state of the collection. The
-following health state values are defined, ordered from the best to worst:
-
-* `GREEN` - all replicas are active, and there's a shard leader
-* `YELLOW` - less than 1/3rd of replicas in a shard is offline, and there's a
shard leader
-* `ORANGE` - more than 1/3rd but less than 2/3rd of replicas in a shard is
offline,
- and there's a shard leader
-* `RED` - more than 2/3rd of replicas is offline, OR there's no shard leader.
+order to make it easier to monitor the operational state of the collections.
The
+following health state values are defined, ordered from the best to worst,
based on
+the percentage of active replicas (`active`):
+
+`GREEN`::
+`active == 100%`, all replicas are active and there's a shard leader.
+`YELLOW`::
+`100% > active > 50%`, AND there's a shard leader.
+`ORANGE`::
+`50% >= active > 1%`, AND there's a shard leader.
+`RED`::
+`1% >= active`, *OR* there's no shard leader.
The collection health state is reported as the worst state of any shard, e.g.
for a
collection with all shards GREEN except for one YELLOW the collection health
will be
