# Request \_cat/shards display index\_closed\_exception

**URL:** <https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992>\
**Category:** Elasticsearch\
**Created:** [December 24, 2018, 9:49am UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992 "2018-12-24T09:49:10Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![test987654123](https://avatars.discourse-cdn.com/v4/letter/t/ecb155/32.png) [@test987654123](https://discuss.elastic.co/u/test987654123)\
**Post date:** [December 24, 2018, 9:49am UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992/1 "2018-12-24T09:49:10Z")

</div>

Hi, My Cluster version is 6.4.2 ， I closed part of the index for storage reasons。  
When I request this api, Response request is index\_closed\_exception 。

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

---

<div class="post-metadata">

**Author:** ![nikhil.k](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@nikhil.k](https://discuss.elastic.co/u/nikhil.k)\
**Post date:** [December 24, 2018, 10:54am UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992/2 "2018-12-24T10:54:34Z")

</div>

Hi @test987654123,

This is correct behaviour. Also, can you be more clear about your query?

Regards  
Nikhil Kapoor

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [December 24, 2018, 11:58am UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992/3 "2018-12-24T11:58:45Z")

</div>

> This is correct behaviour.

I don't think this is a correct behavior. When you close an index, it should not interfer with other APIs IMO.

> My Cluster version is 6.4.2

Could you try with the latest 6.5 version?

---

<div class="post-metadata">

**Author:** ![test987654123](https://avatars.discourse-cdn.com/v4/letter/t/ecb155/32.png) [@test987654123](https://discuss.elastic.co/u/test987654123)\
**Post date:** [December 24, 2018, 1:17pm UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992/4 "2018-12-24T13:17:46Z")

</div>

Upgrade the cluster, I need to migrate hot data,  
But I found that I can't get it Index

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [December 25, 2018, 2:56am UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992/5 "2018-12-25T02:56:39Z")

</div>

Sorry I don't understand what you wrote.  
What do you mean?

---

<div class="post-metadata">

**Author:** ![test987654123](https://avatars.discourse-cdn.com/v4/letter/t/ecb155/32.png) [@test987654123](https://discuss.elastic.co/u/test987654123)\
**Post date:** [December 25, 2018, 3:37am UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992/6 "2018-12-25T03:37:24Z")

</div>

Sorry, I am preparing to migrate the cluster. Because of the hot and cold data separation strategy, some indexes cannot be retrieved directly.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [December 25, 2018, 2:11pm UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992/7 "2018-12-25T14:11:09Z")

</div>

May be just open the closed indices?

---

<div class="post-metadata">

**Author:** ![nikhil.k](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@nikhil.k](https://discuss.elastic.co/u/nikhil.k)\
**Post date:** [December 26, 2018, 4:58am UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992/8 "2018-12-26T04:58:40Z")

</div>

Hi @dadoonet,

Yes, you are right. This is not a correct behaviour.

"index\_closed\_exception" should have been shown, if the index is closed and user have executed the below command:

# curl -X GET "10.x.x.x:9200/\_cat/shards/index\_name"

Where, index\_name is the name of the closed index

Regards  
Nikhil Kapoor

---

<div class="post-metadata">

**Author:** ![test987654123](https://avatars.discourse-cdn.com/v4/letter/t/ecb155/32.png) [@test987654123](https://discuss.elastic.co/u/test987654123)\
**Post date:** [December 27, 2018, 8:18am UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992/9 "2018-12-27T08:18:26Z")

</div>

Hi, The cluster has been upgraded to the latest version, and the problem is still not solved.

---

<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 24, 2019, 8:27am UTC](https://discuss.elastic.co/t/request-cat-shards-display-index-closed-exception/161992/10 "2019-01-24T08:27:04Z")

</div>

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