# Index Helath stay red over 1hour when restore snapshot

**URL:** <https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558>\
**Category:** Elasticsearch\
**Created:** [December 14, 2020, 9:47am UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558 "2020-12-14T09:47:15Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![fujitalon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fujitalon/32/80799_2.png) [@fujitalon](https://discuss.elastic.co/u/fujitalon)\
**Post date:** [December 14, 2020, 9:47am UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558/1 "2020-12-14T09:47:15Z")

</div>

I have 2 ElasticCloud on Azure japaneast and southeastasia.

Try to test failover, I want make snapshot on japaneast, then restore on southeastasia.

I know direct restore didn't support between regions, So I make script to copy blob files from japaneast to southeastasia.  
After copy files, I feel snapshot is OK on southeastasia.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/8/0856c2f5d0be13c04885f47e5bc0fd53bc5b70b0.png)

But after restore snapshot on southeastasia, No snapshot restored status and Index Health is red.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/0/b0117cd9a01a489a93936f04e365267dec3a130e.png)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/8/a830447ea1ccc27eaa04794c0c0ecf123957aed9.png)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/7/d7a19bedf31c207961249b63a9d3c23af36d8068.png)

What's wrong with me?

Thanks.

---

<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:** [December 14, 2020, 9:21pm UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558/2 "2020-12-14T21:21:02Z")

</div>

What is the output from the `_cat/recovery?v` API endpoint?

---

<div class="post-metadata">

**Author:** ![fujitalon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fujitalon/32/80799_2.png) [@fujitalon](https://discuss.elastic.co/u/fujitalon)\
**Post date:** [December 15, 2020, 12:57am UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558/3 "2020-12-15T00:57:51Z")

</div>

@warkolm  
Thank you for your response.

API result is here:  
But red status indices not included.

```auto
.security-tokens-7 0 1.1s peer done 10.46.104.24 instance-0000000000 10.46.104.12 instance-0000000001 n/a n/a 33 33 100.0% 33 80509 80509 100.0% 80509 0 0 100.0%
.security-tokens-7 0 258ms existing_store done n/a n/a 10.46.104.24 instance-0000000000 n/a n/a 0 0 100.0% 33 0 0 100.0% 80509 0 0 100.0%
.kibana-event-log-7.9.3-000001 0 611ms peer done 10.46.104.24 instance-0000000000 10.46.104.12 instance-0000000001 n/a n/a 4 4 100.0% 4 5744 5744 100.0% 5744 0 0 100.0%
.kibana-event-log-7.9.3-000001 0 61ms existing_store done n/a n/a 10.46.104.24 instance-0000000000 n/a n/a 0 0 100.0% 4 0 0 100.0% 5744 0 0 100.0%
.security-7 0 1.3s peer done 10.46.104.24 instance-0000000000 10.46.104.12 instance-0000000001 n/a n/a 39 39 100.0% 39 198259 198259 100.0% 198259 0 0 100.0%
.security-7 0 299ms existing_store done n/a n/a 10.46.104.24 instance-0000000000 n/a n/a 0 0 100.0% 39 0 0 100.0% 198259 0 0 100.0%
.kibana_task_manager_2 0 986ms peer done 10.46.104.24 instance-0000000000 10.46.104.12 instance-0000000001 n/a n/a 27 27 100.0% 27 28047 28047 100.0% 28047 6 6 100.0%
.kibana_task_manager_2 0 97ms existing_store done n/a n/a 10.46.104.24 instance-0000000000 n/a n/a 0 0 100.0% 27 0 0 100.0% 28047 0 0 100.0%
.apm-custom-link 0 641ms peer done 10.46.104.24 instance-0000000000 10.46.104.12 instance-0000000001 n/a n/a 1 1 100.0% 1 261 261 100.0% 261 0 0 100.0%
.apm-custom-link 0 27ms existing_store done n/a n/a 10.46.104.24 instance-0000000000 n/a n/a 0 0 100.0% 1 0 0 100.0% 261 0 0 100.0%
.kibana_task_manager_1 0 759ms peer done 10.46.104.24 instance-0000000000 10.46.104.12 instance-0000000001 n/a n/a 24 24 100.0% 24 22965 22965 100.0% 22965 0 0 100.0%
.kibana_task_manager_1 0 135ms existing_store done n/a n/a 10.46.104.24 instance-0000000000 n/a n/a 0 0 100.0% 24 0 0 100.0% 22965 0 0 100.0%
.apm-agent-configuration 0 613ms peer done 10.46.104.24 instance-0000000000 10.46.104.12 instance-0000000001 n/a n/a 1 1 100.0% 1 261 261 100.0% 261 0 0 100.0%
.apm-agent-configuration 0 36ms existing_store done n/a n/a 10.46.104.24 instance-0000000000 n/a n/a 0 0 100.0% 1 0 0 100.0% 261 0 0 100.0%
.kibana-event-log-7.10.1-000001 0 653ms peer done 10.46.104.24 instance-0000000000 10.46.104.12 instance-0000000001 n/a n/a 4 4 100.0% 4 5792 5792 100.0% 5792 0 0 100.0%
.kibana-event-log-7.10.1-000001 0 60ms existing_store done n/a n/a 10.46.104.24 instance-0000000000 n/a n/a 0 0 100.0% 4 0 0 100.0% 5792 0 0 100.0%
.kibana_2 0 986ms peer done 10.46.104.24 instance-0000000000 10.46.104.12 instance-0000000001 n/a n/a 33 33 100.0% 33 10911883 10911883 100.0% 10911883 0 0 100.0%
.kibana_2 0 301ms existing_store done n/a n/a 10.46.104.24 instance-0000000000 n/a n/a 0 0 100.0% 33 0 0 100.0% 10911883 0 0 100.0%
.kibana_1 0 1.1s peer done 10.46.104.24 instance-0000000000 10.46.104.12 instance-0000000001 n/a n/a 30 30 100.0% 30 10921713 10921713 100.0% 10921713 0 0 100.0%
.kibana_1 0 105ms existing_store done n/a n/a 10.46.104.24 instance-0000000000 n/a n/a 0 0 100.0% 30 0 0 100.0% 10921713 0 0 100.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:** [December 15, 2020, 12:58am UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558/4 "2020-12-15T00:58:53Z")

</div>

What about `_cat/allocation?v`?

---

<div class="post-metadata">

**Author:** ![fujitalon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fujitalon/32/80799_2.png) [@fujitalon](https://discuss.elastic.co/u/fujitalon)\
**Post date:** [December 15, 2020, 2:21am UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558/5 "2020-12-15T02:21:52Z")

</div>

> [@warkolm](#):
>
> \_cat/allocation?v

Response is here:

```auto
15 21.6mb 44.6mb 59.9gb 60gb 0 10.46.104.24 10.46.104.24 instance-0000000000
15 21.9mb 28mb 59.9gb 60gb 0 10.46.104.12 10.46.104.12 instance-0000000001
 4 UNASSIGNED

```

---

<div class="post-metadata">

**Author:** ![fujitalon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fujitalon/32/80799_2.png) [@fujitalon](https://discuss.elastic.co/u/fujitalon)\
**Post date:** [December 16, 2020, 1:36am UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558/6 "2020-12-16T01:36:09Z")

</div>

Just to be sure, I download blobs from japaneast and southeastasia, them compare them.  
No difference found.

---

<div class="post-metadata">

**Author:** ![fujitalon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fujitalon/32/80799_2.png) [@fujitalon](https://discuss.elastic.co/u/fujitalon)\
**Post date:** [December 16, 2020, 2:12am UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558/7 "2020-12-16T02:12:32Z")

</div>

I try with s3 snapshot repository, I got same result (red state indices).

---

<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:** [December 16, 2020, 8:37am UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558/8 "2020-12-16T08:37:54Z")

</div>

If your cluster health is `red` you should always start from the [allocation explain API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-allocation-explain.html). Here is a blog post about diagnosing `red` health:

> **[RED Elasticsearch Cluster? Panic no longer](https://www.elastic.co/blog/red-elasticsearch-cluster-panic-no-longer)**
>
> Your cluster is RED - you have unassigned shards and your cluster is not fully operational. Introducing a new Elasticsearch API which will save the day.

---

<div class="post-metadata">

**Author:** ![fujitalon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fujitalon/32/80799_2.png) [@fujitalon](https://discuss.elastic.co/u/fujitalon)\
**Post date:** [December 16, 2020, 9:25am UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558/9 "2020-12-16T09:25:15Z")

</div>

@DavidTurner  
Thank you for your reply !

I found some plugins are not installed on southeastasia deployment.  
After install plugin, restore is succeeded.

---

<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:** [January 13, 2021, 9:25am UTC](https://discuss.elastic.co/t/index-helath-stay-red-over-1hour-when-restore-snapshot/258558/10 "2021-01-13T09:25:37Z")

</div>

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