# Restart Elasticsearch cluster

**URL:** <https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026>\
**Category:** Elasticsearch\
**Created:** [November 2, 2020, 1:42pm UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026 "2020-11-02T13:42:04Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![WLM](https://avatars.discourse-cdn.com/v4/letter/w/e274bd/32.png) [@WLM](https://discuss.elastic.co/u/WLM)\
**Post date:** [November 2, 2020, 1:42pm UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026/1 "2020-11-02T13:42:04Z")

</div>

Hello  
I have 6 elasticsearch instanse are runnig in docker containers on 3 physical node. When one of the elasticsearch instanse is restrating, all of indexs become inaccessible. How i can fix it? Config of elasticsearch such:

```auto
cluster.name: my-cluster

node.attr.rack: r1
cluster.routing.allocation.awareness.attributes: rack_id

bootstrap.memory_lock: true

network.host: 192.168.1.2

discovery.zen.ping.unicast.hosts: 
    - 192.168.1.2
    - 192.168.1.3
    - 192.168.1.4
    - 192.168.1.5
    - 192.168.1.6
    - 192.168.1.7

discovery.zen.minimum_master_nodes: 4

cluster.initial_master_nodes:
    - node01
    - node02
    - node03
    - node04
    - node05
    - node06

xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.keystore.type: PKCS12
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: cert.p12
xpack.security.transport.ssl.truststore.path: cert.p12
xpack.security.transport.ssl.truststore.type: PKCS12

# Auth method
xpack:
  security:
     authc:
       realms:
          native:
             native1:
                order: 0

```

---

<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:** [November 2, 2020, 11:20pm UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026/2 "2020-11-02T23:20:35Z")

</div>

What do the logs on the master show when you restart the node?

---

<div class="post-metadata">

**Author:** ![WLM](https://avatars.discourse-cdn.com/v4/letter/w/e274bd/32.png) [@WLM](https://discuss.elastic.co/u/WLM)\
**Post date:** [November 3, 2020, 6:19am UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026/3 "2020-11-03T06:19:16Z")

</div>

Elastic logging is not enabled, to enable it , need to restart the nodes. Rebooting each node makes the indexes unavailable for 30 minutes, which is critical for business

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 3, 2020, 6:35am UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026/4 "2020-11-03T06:35:09Z")

</div>

Are your indices configured to have a replica?

---

<div class="post-metadata">

**Author:** ![WLM](https://avatars.discourse-cdn.com/v4/letter/w/e274bd/32.png) [@WLM](https://discuss.elastic.co/u/WLM)\
**Post date:** [November 3, 2020, 7:31am UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026/5 "2020-11-03T07:31:27Z")

</div>

Yes, all indexes have a replica, but when one of the nodes is reloaded, all indexes go into UNASSIGNED status.

Could it be due to the settings rack?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 3, 2020, 7:33am UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026/6 "2020-11-03T07:33:34Z")

</div>

Yes, that could be the case. How is rack\_id set on the different nodes? How many replicas do you have configured? It also looks like you are setting the attribute `rack` but have instead specified `rack_id` to be used. Is this a copy-paste problem or actually in the config?

---

<div class="post-metadata">

**Author:** ![WLM](https://avatars.discourse-cdn.com/v4/letter/w/e274bd/32.png) [@WLM](https://discuss.elastic.co/u/WLM)\
**Post date:** [November 3, 2020, 8:31am UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026/7 "2020-11-03T08:31:22Z")

</div>

Yes, this is the actual config. I also noticed that this attribute differs from the one described here:

> **[Cluster-level shard allocation and routing settings | Elasticsearch Reference...](https://www.elastic.co/guide/en/elasticsearch/reference/7.x/modules-cluster.html#shard-allocation-awareness)**

One index has one replica.

The settings on the other nodes are as follows:  
node01:  
node.attr.rack: r1  
cluster.routing.allocation.awareness.attributes: rack\_id

node02:  
node.attr.rack: r1  
cluster.routing.allocation.awareness.attributes: rack\_id

node03:  
node.attr.rack: r2  
cluster.routing.allocation.awareness.attributes: rack\_id

node04:  
node.attr.rack: r2  
cluster.routing.allocation.awareness.attributes: rack\_id

node05:  
node.attr.rack: r3  
cluster.routing.allocation.awareness.attributes: rack\_id

node06:  
node.attr.rack: r3  
cluster.routing.allocation.awareness.attributes: rack\_id

Nodes node01 and node02 are the first physical server, node03 and node04 are the second, node05 and node06 are the third

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 3, 2020, 8:42am UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026/8 "2020-11-03T08:42:47Z")

</div>

You need to correct that so it is consistent.

---

<div class="post-metadata">

**Author:** ![WLM](https://avatars.discourse-cdn.com/v4/letter/w/e274bd/32.png) [@WLM](https://discuss.elastic.co/u/WLM)\
**Post date:** [November 9, 2020, 9:54am UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026/9 "2020-11-09T09:54:24Z")

</div>

after I fixed parameter _node.attr.rack_ to _node.attr.rack\_id_, the replica indexes were at UNASSIGNED until I returned the parameter _node.attr.rack_ back. There was such an error in the log:  
_node does not contain the awareness attribute [rack]; required attributes cluster setting [cluster.routing.allocation.awareness.attributes=rack_

---

<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:** [December 7, 2020, 9:54am UTC](https://discuss.elastic.co/t/restart-elasticsearch-cluster/254026/10 "2020-12-07T09:54:28Z")

</div>

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