# Unassigned primary and replica shards in marvel indexes **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-monitoring\ **Created:** [October 9, 2015, 11:05pm UTC](https://discuss.elastic.co/t/unassigned-primary-and-replica-shards-in-marvel-indexes/31942 "2015-10-09T23:05:13Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dash](https://avatars.discourse-cdn.com/v4/letter/d/7c8e57/32.png) [@dash](https://discuss.elastic.co/u/dash)\ **Post date:** [October 9, 2015, 11:05pm UTC](https://discuss.elastic.co/t/unassigned-primary-and-replica-shards-in-marvel-indexes/31942/1 "2015-10-09T23:05:14Z")
I use ES-1.7.2. I started the cluster 3-4 days back and have not restarted the cluster at all. After couple of days, Marvel stopped working. When I investigate, I saw some of the primary and replica shards are not assigned. The logs have the following messages almost every minute - 6/ev002.log.2015-10-07:[2015-10-07 23:54:37,318][ERROR][marvel.agent.exporter] [data-6] create failure (index:[.marvel-2015.10.08] type: [node\_stats]): UnavailableShardsException[[.marvel-2015.10.08][0] Primary shard is not active or isn't assigned to a known node. Timeout: [1m], request: org.elasticsearch.action.bulk.BulkShardRequest@262dcb91] Here is the shard allocation: .marvel-2015.10.08 0 r UNASSIGNED .marvel-2015.10.08 0 p UNASSIGNED .marvel-2015.10.07 0 p STARTED 232749 374.5mb 127.0.1.1 data-1 .marvel-2015.10.07 0 r UNASSIGNED .marvel-2015.10.09 0 r UNASSIGNED .marvel-2015.10.09 0 p UNASSIGNED How do I recover from this state? and what could have gone wrong in the first place? Thanks, Dash. ---
**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:** [October 10, 2015, 2:28am UTC](https://discuss.elastic.co/t/unassigned-primary-and-replica-shards-in-marvel-indexes/31942/2 "2015-10-10T02:28:52Z")
Do you have enough disk space left on your node? ---
**Author:** ![dash](https://avatars.discourse-cdn.com/v4/letter/d/7c8e57/32.png) [@dash](https://discuss.elastic.co/u/dash)\ **Post date:** [October 10, 2015, 4:21am UTC](https://discuss.elastic.co/t/unassigned-primary-and-replica-shards-in-marvel-indexes/31942/3 "2015-10-10T04:21:28Z")
Thanks Mark, for the response. Yes, there is still 256GB of space still left on disk. -Dash. ---
**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:** [October 11, 2015, 12:02am UTC](https://discuss.elastic.co/t/unassigned-primary-and-replica-shards-in-marvel-indexes/31942/4 "2015-10-11T00:02:58Z")
You don't happen to have allocation disabled do you? ---
**Author:** ![dash](https://avatars.discourse-cdn.com/v4/letter/d/7c8e57/32.png) [@dash](https://discuss.elastic.co/u/dash)\ **Post date:** [October 11, 2015, 12:21am UTC](https://discuss.elastic.co/t/unassigned-primary-and-replica-shards-in-marvel-indexes/31942/5 "2015-10-11T00:21:19Z")
Hi Mark, was going to update you about this. I have 256G of storage left, but that is in a big drive with 2.5T storage in total. Though Elasticsearch is taking a small fraction of that drive, it hit the 90% watermark. I updated the cluster setting to make the high watermark to 50G, and the shards got assigned. I don't understand why it doesn't assign an existing shard, even when new data is not being added there. But, changing the threshold got me over the hump. Again, thanks for pointing me towards disk problems. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:47pm UTC](https://discuss.elastic.co/t/unassigned-primary-and-replica-shards-in-marvel-indexes/31942/6 "2017-07-06T13:47:30Z")