# Bringing Elasticsearch node back online after being offline for a week

**URL:** <https://discuss.elastic.co/t/bringing-elasticsearch-node-back-online-after-being-offline-for-a-week/312497>\
**Category:** Elasticsearch\
**Created:** [August 19, 2022, 7:07pm UTC](https://discuss.elastic.co/t/bringing-elasticsearch-node-back-online-after-being-offline-for-a-week/312497 "2022-08-19T19:07:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kossde](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@kossde](https://discuss.elastic.co/u/kossde)\
**Post date:** [August 19, 2022, 7:07pm UTC](https://discuss.elastic.co/t/bringing-elasticsearch-node-back-online-after-being-offline-for-a-week/312497/1 "2022-08-19T19:07:57Z")

</div>

We have an Elasticsearch data node that has been offline for a week. If we bring this node back online, will the cluster try to create new replica shards for the old primaries stored on that node or, because the shards are old, will it just dump them and allocate updated shards accordingly?

---

<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:** [August 20, 2022, 4:46am UTC](https://discuss.elastic.co/t/bringing-elasticsearch-node-back-online-after-being-offline-for-a-week/312497/2 "2022-08-20T04:46:09Z")

</div>

Which version of Elasticsearch are you using?

---

<div class="post-metadata">

**Author:** ![kossde](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@kossde](https://discuss.elastic.co/u/kossde)\
**Post date:** [September 4, 2022, 3:20pm UTC](https://discuss.elastic.co/t/bringing-elasticsearch-node-back-online-after-being-offline-for-a-week/312497/3 "2022-09-04T15:20:45Z")

</div>

7.13.2 is the version

---

<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:** [September 4, 2022, 5:45pm UTC](https://discuss.elastic.co/t/bringing-elasticsearch-node-back-online-after-being-offline-for-a-week/312497/4 "2022-09-04T17:45:15Z")

</div>

If a node leaves the cluster, any indices having primary shards on this node will have a replica present on other node in the cluster promoted to primary. If there are no replicas you will see the index enter the red state. When the node later comes back into the cluster the indices will likely be out of date and be brought up to the current state or simply replaced with up to date replicas.

The cluster will handle this automatically.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [September 4, 2022, 6:28pm UTC](https://discuss.elastic.co/t/bringing-elasticsearch-node-back-online-after-being-offline-for-a-week/312497/5 "2022-09-04T18:28:16Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> The cluster will handle this automatically.

I agree with @Christian_Dahlqvist ... just will add a few caveats... 🙂

- Assuming no other issues
- You have enough capacity on all node etc (CPU, RAM, Network, Disk)
- You are patient enough to let it settle 🙂 depending on the Size, Number or Indices / Shards etc.

---

<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:** [October 2, 2022, 6:28pm UTC](https://discuss.elastic.co/t/bringing-elasticsearch-node-back-online-after-being-offline-for-a-week/312497/6 "2022-10-02T18:28:58Z")

</div>

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