Elasticsearch operator logs timeout error when trying to rollout changes to the cluster
Issue
-
When a change if performed in the Service Mesh Control Plane (SMCP) object that affects the settings of the Elasticsearch cluster (for example modifying the memory) the Elasticsearch operator starts reconciling the cluster to apply the changes.
tracing.jaeger.elasticsearch: container: resources: limits: memory: 3Gi requests: cpu: 250m memory: 1Gi -
A timeout error will be seen in the Elasticsearch operator logs and the rolling update never completes. An error message like this can be seen:
{"_ts":"2023-08-09T06:48:43.716516978Z","_level":"0","_component":"elasticsearch-operator_controllers_Elasticsearch","_message":"failed to perform rolling update","_error":{"msg":"timed out waiting for node to rollout","node":"elasticsearch-cdm-istiosystemjaeger-1"},"cluster":"elasticsearch","namespace":"istio-system"} -
The Elasticsearch cluster state will not be shown as
green.
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4.x
- Red Hat OpenShift Service Mesh
- 2.x
- Red Hat OpenShift Elasticsearch Operator
- 5.7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.