# Reroute unassigned shards **URL:** \ **Category:** Elasticsearch\ **Created:** [February 20, 2018, 4:50pm UTC](https://discuss.elastic.co/t/reroute-unassigned-shards/120686 "2018-02-20T16:50:33Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [February 21, 2018, 11:13am UTC](https://discuss.elastic.co/t/reroute-unassigned-shards/120686/4 "2018-02-21T11:13:22Z")
Read [this](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) and specifically the "Also be patient" part. Elasticsearch will never assign a primary shard and its replica to the same node, so if you only have one node you will never be able to allocate any configured replica shards. Ways to remove the unassigned shard would be to add another node to the cluster or set the number of replicas to 0 for all indices. If you have unassigned primary shards, have a look at [this blog post](https://www.elastic.co/blog/red-elasticsearch-cluster-panic-no-longer). --- _[View the full topic](https://discuss.elastic.co/t/reroute-unassigned-shards/120686)._