# Termination of the restore process via index deletion doesn't cleanup index data
**URL:** https://discuss.elastic.co/t/termination-of-the-restore-process-via-index-deletion-doesnt-cleanup-index-data/36038
**Category:** Elasticsearch
**Created:** [December 1, 2015, 12:03pm UTC](https://discuss.elastic.co/t/termination-of-the-restore-process-via-index-deletion-doesnt-cleanup-index-data/36038 "2015-12-01T12:03:21Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Anatoly\_Petkevich](https://discuss.elastic.co/u/Anatoly_Petkevich)
#### Post date: [December 1, 2015, 12:03pm UTC](https://discuss.elastic.co/t/termination-of-the-restore-process-via-index-deletion-doesnt-cleanup-index-data/36038/1 "2015-12-01T12:03:21Z")
According to [https://www.elastic.co/guide/en/elasticsearch/reference/1.7/modules-snapshots.html](https://www.elastic.co/guide/en/elasticsearch/reference/1.7/modules-snapshots.html), termination of restore operation via index deletion should ensure that "data for all deleted indices will be removed from the cluster".
The version of Elasticsearch we use is 1.7.2 and after deletion of rather large index that was being restored no disk space was freed and index files still do exist.
Is this a bug or documentation inconsistency?
Thanks in advance.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:34pm UTC](https://discuss.elastic.co/t/termination-of-the-restore-process-via-index-deletion-doesnt-cleanup-index-data/36038/2 "2017-07-05T23:34:29Z")