Erreur de démarrage d'Elasticsearch avec le code de sortie 137 dans le déploiement datamulti -nœudsmaster

Elastic Stack Beats
, , , ,
1

Hello,

I am currently encountering an issue with deploying two Elasticsearch nodes, a data nodemaster

ERROR: Elasticsearch died while starting up, with exit code 137

I have set up the jvm.options file to define JVM parameters (especially memory), but the error persists.

Here are the main steps I’ve followed so far:

  1. Deployed two separate StatefulSets for the data and master nodes using the image docker.elastic.co/elasticsearch/elasticsearch:8.13.4.
  2. Configured environment variables to define the cluster name and discovery hosts.
  3. Mounted the elasticsearch.yml and jvm.options files via ConfigMap in the corresponding pods.
  4. Adj

I’ve checked the following without success:

  • The configuration files are correctly mounted and readable
  • The allocated resources seem sufficient (1 GB of RAM minimum, with CPU usage limited).
  • The startup logs show that Elasticsearch attempts to start but fails with an exit code 137, which typically indicates a memory issue or an error during JV

I would appreciate your assistance in identifying the root cause of this error and if any additional adjustments to

Thank you in advance for your suggestions and assistance.

Best regards,