# Hot-warm 'move index' does not delete index data from original node
**URL:** https://discuss.elastic.co/t/hot-warm-move-index-does-not-delete-index-data-from-original-node/63052
**Category:** Elasticsearch
**Created:** [October 14, 2016, 11:59am UTC](https://discuss.elastic.co/t/hot-warm-move-index-does-not-delete-index-data-from-original-node/63052 "2016-10-14T11:59:11Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@currycoder](https://discuss.elastic.co/u/currycoder)
#### Post date: [October 14, 2016, 11:59am UTC](https://discuss.elastic.co/t/hot-warm-move-index-does-not-delete-index-data-from-original-node/63052/1 "2016-10-14T11:59:11Z")
Hello,
I'm experimenting with introducing a 'warm' data node as explained here: [https://www.elastic.co/blog/hot-warm-architecture](https://www.elastic.co/blog/hot-warm-architecture)
I've allocated my indices to my 'hot' node and have attempted to move a single index to my 'warm' node, which appears to have been successful. I moved an index called `analytics-pageview-2016-08-30` - here's the pertinent output from `/cat/_shards`:
```auto
analytics-pageview-2016-09-20 1 p STARTED 967053 297.9mb 10.196.3.254 Ocean
analytics-pageview-2016-09-20 1 r UNASSIGNED
analytics-pageview-2016-09-20 0 p STARTED 966107 298.1mb 10.196.3.254 Ocean
analytics-pageview-2016-09-20 0 r UNASSIGNED
analytics-pageview-2016-08-30 1 p STARTED 841559 256.9mb 10.1.0.61 Lady Octopus
analytics-pageview-2016-08-30 1 r UNASSIGNED
analytics-pageview-2016-08-30 0 p STARTED 842086 255.9mb 10.1.0.61 Lady Octopus
analytics-pageview-2016-08-30 0 r UNASSIGNED
analytics-pageview-2016-08-31 1 p STARTED 920134 279.2mb 10.196.3.254 Ocean
analytics-pageview-2016-08-31 1 r UNASSIGNED
analytics-pageview-2016-08-31 0 p STARTED 919752 284.1mb 10.196.3.254 Ocean
analytics-pageview-2016-08-31 0 r UNASSIGNED
```
However on my 'hot' node, I can still see that index's data:
```auto
$ du -sh /var/lib/elasticsearch/elasticsearch/nodes/0/indices/analytics-pageview-2016-08-30
514M /var/lib/elasticsearch/elasticsearch/nodes/0/indices/analytics-pageview-2016-08-30
```
Will this eventually be cleaned up by elasticsearch following some criteria being satisfied?
I'd greatly appreciate any advice you could offer.
---
### Author:  [@ywelsch](https://discuss.elastic.co/u/ywelsch)
#### Post date: [October 14, 2016, 1:05pm UTC](https://discuss.elastic.co/t/hot-warm-move-index-does-not-delete-index-data-from-original-node/63052/2 "2016-10-14T13:05:53Z")
> [@currycoder](#):
>
> Will this eventually be cleaned up by elasticsearch following some criteria being satisfied?
yes, the criteria is that there are enough shard copies in the cluster. You specified that shards of this index must have 1 replica. In your current cluster, only the primary is allocated. As long as no replica is allocated, the cluster will keep the extra copy of the data around.
---
### Author:  [@currycoder](https://discuss.elastic.co/u/currycoder)
#### Post date: [October 14, 2016, 1:27pm UTC](https://discuss.elastic.co/t/hot-warm-move-index-does-not-delete-index-data-from-original-node/63052/3 "2016-10-14T13:27:59Z")
Ah - that makes sense. Thanks for taking the time to answer.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:12pm UTC](https://discuss.elastic.co/t/hot-warm-move-index-does-not-delete-index-data-from-original-node/63052/4 "2017-07-05T22:12:18Z")