# Elasticsearch upgrade from 7.6 to 7.13

**URL:** <https://discuss.elastic.co/t/elasticsearch-upgrade-from-7-6-to-7-13/276146>\
**Category:** Elasticsearch\
**Tags:** painless\
**Created:** [June 16, 2021, 1:15pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-7-6-to-7-13/276146 "2021-06-16T13:15:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thewasta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thewasta/32/48818_2.png) [@thewasta](https://discuss.elastic.co/u/thewasta)\
**Post date:** [June 16, 2021, 1:15pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-7-6-to-7-13/276146/1 "2021-06-16T13:15:48Z")

</div>

S.O: Ubuntu 18.04  
ES: 7.6.1 (Before upgrade)

I tried to upgrade my ElasticStack with 3 nodes (1 master, 2 slave).

Following the [Guide](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html). And all of those steps are only on master.  
here my steps:

```auto
curl -XPUT -u elastic:changeme "localhost:9200/_cluster/settings?pretty" -H 'Content-Type: application/json' -d'
{
  "persistent": {
    "cluster.routing.allocation.enable": "primaries"
  }
}
'

```

```auto
curl -XPOST -u elastic:changeme "localhost:9200/_flush/synced?pretty"

```

```auto
service elasticsearch stop

```

```auto
apt-get update && apt-get install elasticsearch

```

Eventually this asked for override my `elasticsearch.yml` file, I pressed "N".  
And then tried to start elastic but got error:

```auto
[2021-06-16T13:06:56,069][INFO][o.e.i.g.DatabaseRegistry] [master] initialized database registry, using geoip-databases directory [/tmp/elasticsearch-1576930118492589462/geoip-databases/V3a78v1XTUWzHmDr52dZBA]
[2021-06-16T13:06:57,054][INFO][o.e.t.NettyAllocator] [master] creating NettyAllocator with the following configs: [name=unpooled, suggested_max_allocation_size=1mb, factors={es.unsafe.use_unpooled_allocator=null, g1gc_enabled=true, g1gc_region_size=4mb, heap_size=1gb}]
[2021-06-16T13:06:57,168][INFO][o.e.d.DiscoveryModule] [master] using discovery type [zen] and seed hosts providers [settings]
[2021-06-16T13:06:57,911][INFO][o.e.g.DanglingIndicesState] [master] gateway.auto_import_dangling_indices is disabled, dangling indices will not be automatically detected or imported and must be managed manually
[2021-06-16T13:06:58,707][INFO][o.e.n.Node] [master] initialized
[2021-06-16T13:06:58,709][INFO][o.e.n.Node] [master] starting ...
[2021-06-16T13:06:58,854][INFO][o.e.x.s.c.f.PersistentCache] [master] persistent cache index loaded
[2021-06-16T13:06:59,078][INFO][o.e.t.TransportService] [master] publish_address {192.168.1.76:9300}, bound_addresses {127.0.0.1:9300}, {[::1]:9300}, {192.168.1.76:9300}
[2021-06-16T13:07:00,592][INFO][o.e.b.BootstrapChecks] [master] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2021-06-16T13:07:00,601][ERROR][o.e.b.Bootstrap] [master] node validation exception
[1] bootstrap checks failed. You must address the points described in the following [1] lines before starting Elasticsearch.
bootstrap check failure [1] of [1]: memory locking requested for elasticsearch process but memory is not locked
[2021-06-16T13:07:00,632][INFO][o.e.n.Node] [master] stopping ...
[2021-06-16T13:07:00,718][INFO][o.e.n.Node] [master] stopped
[2021-06-16T13:07:00,723][INFO][o.e.n.Node] [master] closing ...
[2021-06-16T13:07:00,769][INFO][o.e.n.Node] [master] closed
[2021-06-16T13:07:00,771][INFO][o.e.x.m.p.NativeController] [master] Native controller process has stopped - no new native processes can be started

```

This is `elasticsearch.yml` file

```auto
cluster.name: cluster
node.name: master
reindex.remote.whitelist: '192.168.1.142:9200'
node.master: true
#node.data: true
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: ["localhost", "192.168.1.76"]
#discovery.seed_host: ["192.168.1.76", "192.168.1.77", "192.168.1.78"]
cluster.initial_master_nodes: ["192.168.1.76", "192.168.1.77", "192.168.1.78"]
#discovery.zen.ping.unicast.hosts: ["192.168.1.76", "192.168.1.77", "192.168.1.78"]
discovery.seed_hosts: ["192.168.1.76", "192.168.1.77", "192.168.1.78"]
bootstrap.memory_lock: true
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: elastic-certificates.p12
xpack.security.transport.ssl.truststore.path: elastic-certificates.p12

script.painless.regex.enabled: true

```

And file `/etc/default/elasticsearch` I have `MAX_LOCKED_MEMORY=infinity`

Thanks

---

<div class="post-metadata">

**Author:** ![thewasta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thewasta/32/48818_2.png) [@thewasta](https://discuss.elastic.co/u/thewasta)\
**Post date:** [June 16, 2021, 2:24pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-7-6-to-7-13/276146/2 "2021-06-16T14:24:31Z")

</div>

> # Solution:

```auto
$ systemctl edit elasticsearch

```

Write line

```auto
[Service]
LimitMEMLOCK=infinity

```

And

```auto
$ systemctl daemon-reload 
$ systemctl restart elasticsearch

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 17, 2021, 1:09am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-7-6-to-7-13/276146/3 "2021-06-17T01:09:24Z")

</div>

Thanks for sharing your solution!

Also please note that there is no such thing as a slave in Elasticsearch 🙂

---

<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:** [July 15, 2021, 1:09am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-7-6-to-7-13/276146/4 "2021-07-15T01:09:33Z")

</div>

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