forked from elastic/elasticsearch
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Inactive replica of new primary shard is green (elastic#99995)
When we have a new initialisation of a primary shard we consider the this indicator `green` based on the idea that this are unexceptional events in the cluster's lifecycle. However, when we have a replica of this shard that is inactive we turn to `yellow`. With this PR, we change this behaviour to signal that if the primary is inactive and that is `green`, then an inactive replica of this shard is also `green`. Fixes elastic#99951
- Loading branch information
Showing
3 changed files
with
28 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
pr: 99995 | ||
summary: When a primary is inactive but this is considered expected, the same applies for the replica of this shard. | ||
area: Health | ||
type: enhancement | ||
issues: | ||
- 99951 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters