Skip to content
This repository was archived by the owner on Sep 21, 2021. It is now read-only.

Commit d384748

Browse files
ericamickpolyfractal
authored andcommitted
Update 20_health.asciidoc (#521)
1 parent 97f43de commit d384748

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

500_Cluster_Admin/20_health.asciidoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ high availability is compromised to some degree. If _more_ shards disappear, yo
5050
might lose data. Think of `yellow` as a warning that should prompt investigation.
5151

5252
`red`::
53-
At least one primary shard (and all of its replicas) are missing. This means
53+
At least one primary shard (and all of its replicas) is missing. This means
5454
that you are missing data: searches will return partial results, and indexing
5555
into that shard will return an exception.
5656

@@ -205,7 +205,7 @@ This is important for automated scripts and tests.
205205

206206
If you create an index, Elasticsearch must broadcast the change in cluster state
207207
to all nodes. Those nodes must initialize those new shards, and then respond to the
208-
master that the shards are `Started`. This process is fast, but because network
208+
master that the shards are `Started`. This process is fast, but because of network
209209
latency may take 10–20ms.
210210

211211
If you have an automated script that (a) creates an index and then (b) immediately

0 commit comments

Comments
 (0)