# Elasticsearch:7.11.0 bootstrap checks failed

**URL:** <https://discuss.elastic.co/t/elasticsearch-7-11-0-bootstrap-checks-failed/264733>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [February 18, 2021, 4:23pm UTC](https://discuss.elastic.co/t/elasticsearch-7-11-0-bootstrap-checks-failed/264733 "2021-02-18T16:23:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rp346](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rp346/32/53882_2.png) [@rp346](https://discuss.elastic.co/u/rp346)\
**Post date:** [February 18, 2021, 4:23pm UTC](https://discuss.elastic.co/t/elasticsearch-7-11-0-bootstrap-checks-failed/264733/1 "2021-02-18T16:23:49Z")

</div>

I upgraded elastic-search cluster from `elasticsearch:7.10.0` to `elasticsearch:7.11.0` and started noticing following error

```auto
{"type": "server", "timestamp": "2021-02-18T16:15:46,270Z", "level": "INFO", "component": "o.e.b.BootstrapChecks", "cluster.name": "dev-eks-logs", "node.name": "es-master-2.elasticsearch", "message": "bound or publishing to a non-loopback address, enforcing bootstrap checks" }
ERROR: [1] bootstrap checks failed
[1]: initial heap size [41943040] not equal to maximum heap size [1073741824]; this can cause resize pauses
ERROR: Elasticsearch did not exit normally - check the logs at /usr/share/elasticsearch/logs/dev-eks-logs.log
{"type": "server", "timestamp": "2021-02-18T16:15:46,315Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "dev-eks-logs", "node.name": "es-master-2.elasticsearch", "message": "stopping ..." }
{"type": "server", "timestamp": "2021-02-18T16:15:46,389Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "dev-eks-logs", "node.name": "es-master-2.elasticsearch", "message": "stopped" }
{"type": "server", "timestamp": "2021-02-18T16:15:46,389Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "dev-eks-logs", "node.name": "es-master-2.elasticsearch", "message": "closing ..." }
{"type": "server", "timestamp": "2021-02-18T16:15:46,402Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "dev-eks-logs", "node.name": "es-master-2.elasticsearch", "message": "closed" }
{"type": "server", "timestamp": "2021-02-18T16:15:46,404Z", "level": "INFO", "component": "o.e.x.m.p.NativeController", "cluster.name": "dev-eks-logs", "node.name": "es-master-2.elasticsearch", "message": "Native controller process has stopped - no new native processes can be started" }

```

Then all nodes goes into crashing cycle.

Here is my deployment manifest

> **StatefulSet**
>
> ```auto
> kind: StatefulSet
> apiVersion: apps/v1
> metadata:
> name: es-master
> namespace: kube-logging
> spec:
> serviceName: elasticsearch
> replicas: 3
> updateStrategy:
> type: RollingUpdate
> selector:
> matchLabels:
> app: elasticsearch
> template:
> metadata:
> labels:
> app: elasticsearch
> spec:
> containers:
> - name: elasticsearch
> image: docker.elastic.co/elasticsearch/elasticsearch:7.11.0
> resources:
> limits:
> cpu: 1000m
> memory: 2.5G
> requests:
> cpu: 100m
> ports:
> - containerPort: 9200
> name: rest
> protocol: TCP
> - containerPort: 9300
> name: inter-node
> protocol: TCP
> # readinessProbe:
> # httpGet:
> # path: /_cluster/health?local=true
> # port: 9200
> # initialDelaySeconds: 5
> volumeMounts:
> - name: data
> mountPath: /usr/share/elasticsearch/data
> env:
> - name: cluster.name
> value: dev-eks-logs
> - name: NODE_NAME
> valueFrom:
> fieldRef:
> fieldPath: metadata.name
> - name: node.name
> value: "$(NODE_NAME).elasticsearch"
> - name: discovery.zen.ping.unicast.hosts
> value: "es-master-0.elasticsearch,es-master-1.elasticsearch,es-master-2.elasticsearch"
> - name: cluster.initial_master_nodes
> value: "es-master-0.elasticsearch,es-master-1.elasticsearch,es-master-2.elasticsearch"
> - name: discovery.zen.minimum_master_nodes
> value: "2"
> - name: ES_JAVA_OPTS
> value: "-Xmx1g -Xmx1g"
> initContainers:
> - name: fix-permissions
> image: busybox
> command: ["sh", "-c", "chown -R 1000:1000 /usr/share/elasticsearch/data"]
> securityContext:
> privileged: true
> volumeMounts:
> - name: data
> mountPath: /usr/share/elasticsearch/data
> - name: increase-vm-max-map
> image: busybox
> command: ["sysctl", "-w", "vm.max_map_count=262144"]
> securityContext:
> privileged: true
> - name: increase-fd-ulimit
> image: busybox
> command: ["sh", "-c", "ulimit -n 65536"]
> securityContext:
> privileged: true
> volumeClaimTemplates:
> - metadata:
> name: data
> labels:
> app: elasticsearch
> spec:
> accessModes: ["ReadWriteOnce"]
> storageClassName: aws-gp2
> resources:
> requests:
> storage: 200Gi
> 
> ```

any suggestion how to fix this ?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 18, 2021, 4:53pm UTC](https://discuss.elastic.co/t/elasticsearch-7-11-0-bootstrap-checks-failed/264733/2 "2021-02-18T16:53:49Z")

</div>

> [@rp346](#):
>
> `initial heap size [41943040] not equal to maximum heap size [1073741824]`

As the message indicates, you must set the initial heap size (`-Xms`) to equal the maximum heap size (`-Xmx`).

---

<div class="post-metadata">

**Author:** ![rp346](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rp346/32/53882_2.png) [@rp346](https://discuss.elastic.co/u/rp346)\
**Post date:** [February 18, 2021, 5:24pm UTC](https://discuss.elastic.co/t/elasticsearch-7-11-0-bootstrap-checks-failed/264733/3 "2021-02-18T17:24:03Z")

</div>

In my manifest, I am setting this

```auto
          - name: ES_JAVA_OPTS
            value: "-Xmx1g -Xmx1g"

```

Isn't this right place to set this property

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 18, 2021, 5:49pm UTC](https://discuss.elastic.co/t/elasticsearch-7-11-0-bootstrap-checks-failed/264733/4 "2021-02-18T17:49:35Z")

</div>

Looks like the right place, but you're setting `-Xmx` twice and `-Xms` not at all.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 18, 2021, 5:49pm UTC](https://discuss.elastic.co/t/elasticsearch-7-11-0-bootstrap-checks-failed/264733/5 "2021-03-18T17:49:55Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.