# Shard relocation: shard not deleted from original node
**URL:** https://discuss.elastic.co/t/shard-relocation-shard-not-deleted-from-original-node/60650
**Category:** Elasticsearch
**Created:** [September 15, 2016, 9:38pm UTC](https://discuss.elastic.co/t/shard-relocation-shard-not-deleted-from-original-node/60650 "2016-09-15T21:38:55Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@talvey](https://discuss.elastic.co/u/talvey)
#### Post date: [September 15, 2016, 9:38pm UTC](https://discuss.elastic.co/t/shard-relocation-shard-not-deleted-from-original-node/60650/1 "2016-09-15T21:38:55Z")
I'm running into a problematic scenario where upon shard relocation, the original shard is never removed from the originating node.
Scenario Details:
1. Diskspace high watermark is exceeded on a node
2. To alleviate, cluster moves shard to a new node
3. Move is successful (shard active on new node)
4. Original shard is orphaned (data still exists on disk)
Other details:
1. ES 1.7.4
2. Cluster is currently running with allocation set to primaries (this is necessary for the short term)
3. Index is defined with number of replicas = 1 (primary + 1 replica)
4. Logging show s no errors and appears to be removing the shard
Does anyone have an idea how to address this? When removing "moved" shards from a node, does the cluster need to confirm both shard copies are allocated and active before deletion occurs?
Thank you!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:19pm UTC](https://discuss.elastic.co/t/shard-relocation-shard-not-deleted-from-original-node/60650/2 "2017-07-05T22:19:54Z")