# Shard data left on disk after MOVE

**URL:** <https://discuss.elastic.co/t/shard-data-left-on-disk-after-move/65578>\
**Category:** Elasticsearch\
**Created:** [November 10, 2016, 3:47am UTC](https://discuss.elastic.co/t/shard-data-left-on-disk-after-move/65578 "2016-11-10T03:47:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![klahnakoski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/klahnakoski/32/3679_2.png) [@klahnakoski](https://discuss.elastic.co/u/klahnakoski)\
**Post date:** [November 10, 2016, 3:47am UTC](https://discuss.elastic.co/t/shard-data-left-on-disk-after-move/65578/1 "2016-11-10T03:47:59Z")

</div>

I have many nodes (version 1.7.1), and I disabled shard shard balancing:

```
"cluster.routing.allocation.enable": "none"

```

I then move a shard from one node to another using `/_cluster/reroute`, which is successful.

The problem is the data for the shard remains on the original node

```
/data4/mycluster/nodes/0/indices/myindex/15

```

After many moves, both in and out of a node, and across many different indexes, the drive fills up. I must login to the node, and delete the directories for shards that have long left that node to free up space.

Is there a setting that will remove data from disk for shards that do not exist?

thanks

---

<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:** [December 8, 2016, 3:48am UTC](https://discuss.elastic.co/t/shard-data-left-on-disk-after-move/65578/2 "2016-12-08T03:48:24Z")

</div>

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