Is anyone else experiencing problems restarting their older version <7.2 elastic cloud cluster?
I am following the recommendation for the Log4j vulnerability, which is for cloud users to restart their clusters. But in my case, it is not passing the 'Validating prerequisites' step.
Deployments hosted in Elastic Cloud have been updated to leverage the JVM Option -Dlog4j2.formatMsgNoLookups=true which will take effect on restart of the deployment and on any config change to the Elasticsearch deployment.
For users running a cluster on a minor version older than 7.2, we recommend a restart.
The simplest way to restart a deployment is to do the following:
Log in to the Cloud UI. Navigate to the “deployments” section in Elasticsearch Service.
Select the deployment you’d like to restart.
In the “manage” menu, select “restart”. Any kind of restart will work: “no downtime” restarts are fine.
Hi dadoonet,
I do have a ticket open with Elastic, but it is looking like they will take the 72h to get to it, not exactly to have it solved.
And at this point, I can't even see the snapshots on the dashboard anymore.
Hi stephenb,
I did try restarting multiple times, and with different configuration also. Nothing worked
Earlier today there was a restart requested by 'system' and the cluster is online again. I am waiting on support to learn what was the issue.
But at this point, I am afraid of restarting other clusters.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.