Skip to content

Commit f5e1767

Browse files
committed
updated conditions per ewolinetz
1 parent 61a8143 commit f5e1767

File tree

1 file changed

+12
-42
lines changed

1 file changed

+12
-42
lines changed

modules/efk-logging-elasticsearch-status.adoc

Lines changed: 12 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -57,8 +57,15 @@ status: <1>
5757
----
5858
<1> In the output, the cluster status fields appear in the `status` stanza.
5959
<2> The status of the Elasticsearch cluster, `green`, `red`, `yellow`.
60-
<3> Any status conditions, if present.
61-
<4> The Elsticsearch nodes in the cluster, with `upgradeStatus`.
60+
<3> Any status conditions, if present. Any events related to the following conditions are shown:
61+
+
62+
* Container Waiting for both the Elasticsearch and proxy containers,
63+
* Container Terminated for both the Elasticsearch and proxy containers,
64+
* Pod unschedulable.
65+
+
66+
Also, a condition is shown if the node storage passes the high or low watermark thresholds.
67+
68+
<4> The Elasticsearch nodes in the cluster, with `upgradeStatus`.
6269
<5> The Elasticsearch client, data, and master pods in the cluster, listed under 'failed`, `notReady` or `ready` state.
6370

6471
. To view the status of the Elasticsearch deployment configuration:
@@ -191,50 +198,13 @@ Conditions:
191198
Events: <none>
192199
----
193200

194-
== Viewing Elasticsearch cluster status
195-
201+
[id="efk-logging-elasticsearch-status-message{context}"]
202+
== Example condition messages
196203

204+
The following are exemples of some condtion messaages from the `Status.Nodes` section of the Elasticsearch instance.
197205

198206
// https://github.com/openshift/elasticsearch-operator/pull/92
199207

200-
201-
[cols="3,4",options="header"]
202-
|===
203-
| Condition
204-
| Reason
205-
206-
207-
| Invalid master nodes count. Please ensure there are no more than 3 total nodes with master roles
208-
|
209-
210-
| No data nodes requested. Please ensure there is at least 1 node with data roles
211-
|
212-
213-
| Wrong RedundancyPolicy selected. Choose different RedundancyPolicy or add more nodes with data roles
214-
|
215-
216-
| Config Map is different
217-
|
218-
219-
| ScalingUp
220-
|
221-
222-
| ScalingDown
223-
|
224-
225-
| Restarting
226-
|
227-
228-
| Disk Watermark High
229-
| Shards will be relocated from this node
230-
231-
| Disk Watermark Low
232-
| Shards will be not be allocated on this node.
233-
234-
|===
235-
236-
Example conditions
237-
238208
----
239209
nodes:
240210
- conditions:

0 commit comments

Comments
 (0)