# The shard cannot be allocated to the same node on which a copy of the shard already exist

**URL:** https://discuss.elastic.co/t/the-shard-cannot-be-allocated-to-the-same-node-on-which-a-copy-of-the-shard-already-exist/227512
**Category:** Elasticsearch
**Created:** [April 10, 2020, 1:48pm UTC](https://discuss.elastic.co/t/the-shard-cannot-be-allocated-to-the-same-node-on-which-a-copy-of-the-shard-already-exist/227512 "2020-04-10T13:48:34Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![chauchse](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chauchse/32/66112_2.png) [@chauchse](https://discuss.elastic.co/u/chauchse)
#### Post date: [April 10, 2020, 1:48pm UTC](https://discuss.elastic.co/t/the-shard-cannot-be-allocated-to-the-same-node-on-which-a-copy-of-the-shard-already-exist/227512/1 "2020-04-10T13:48:34Z")

</div>

Dear,

I have a strange probleme with elasticsearch (v6.8.8) on ubuntu-server  
I have several indexes on one unique node.

`_cat/indices?v `:

```
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open gl-system-events_0 rmkGOB-9TL6Fh-TGTnGxcA 4 0 0 0 1kb 1kb
yellow open elastalert_status_status RZLm4vyQTuukhhpAPZ1Y6A 5 1 0 0 1.2kb 1.2kb
yellow open elastalert_status_silence IHZgj28FTV-O8J31pZcb5Q 5 1 0 0 1.2kb 1.2kb
yellow open elastalert_status 02oyKzFpQ2KBxg9epcDiGA 5 1 0 0 1.2kb 1.2kb
yellow open elastalert_status_error vXlmQ5oCTr6OIi68kqHPsw 5 1 0 0 1.2kb 1.2kb
green open gl-events_0 lTkAMPFGTvqKwEnEUzqPXQ 4 0 0 0 1kb 1kb
yellow open elastalert_status_past aKBCLAs3Sze6CzToFNuftA 5 1 0 0 1.2kb 1.2kb
green open custom-indice_0 1vQdWQHsQAmAShVxIRdD8g 4 0 149 0 1.7mb 1.7mb

```

`_cluster/allocation/explain?pretty` :

| index | "elastalert\_status" |
| --- | --- |
| shard | 1 |
| primary | false |
| current\_state | "unassigned" |
| unassigned\_info | |
| reason | "INDEX\_CREATED" |
| at | "2020-04-10T13:14:49.767Z" |
| last\_allocation\_status | "no\_attempt" |
| can\_allocate | "no" |
| allocate\_explanation | "cannot allocate because allocation is not permitted to any of the nodes" |
| node\_allocation\_decisions | |
| 0 | |
| node\_id | "FX5I0KjPRk2m4CwbqIB68g" |
| node\_name | "FX5I0Kj" |
| transport\_address | "X.X.X.X:9300" |
| node\_decision | "no" |
| weight\_ranking | 1 |
| deciders | |
| 0 | |
| decider | "same\_shard" |
| decision | "NO" |
| explanation | "the shard cannot be allocated to the same node on which a copy of the shard already exists [[elastalert\_status][1], node[FX5I0KjPRk2m4CwbqIB68g], [P], s[STARTED], a[id=pnuCvhWJSYWvjQXbnOzzhg]]" |

I have tried to reset all data by `curl -XDELETE X.X.X.X:9200/_all` and recreate index, but i still have the same problem.

Thanks for your help.

---

<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: [May 8, 2020, 1:48pm UTC](https://discuss.elastic.co/t/the-shard-cannot-be-allocated-to-the-same-node-on-which-a-copy-of-the-shard-already-exist/227512/2 "2020-05-08T13:48:34Z")

</div>

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