# Issue while installing curator
**URL:** https://discuss.elastic.co/t/issue-while-installing-curator/37714
**Category:** Elasticsearch
**Created:** [December 21, 2015, 7:40pm UTC](https://discuss.elastic.co/t/issue-while-installing-curator/37714 "2015-12-21T19:40:30Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@NiteshBarnwal](https://discuss.elastic.co/u/NiteshBarnwal)
#### Post date: [December 21, 2015, 7:40pm UTC](https://discuss.elastic.co/t/issue-while-installing-curator/37714/1 "2015-12-21T19:40:30Z")
I have configured ELK (elasticsearch 1.7.2) by unzipping the packages. Now I want to install curator. I have below packages.
click-5.1.tar.gz
elasticsearch-curator-3.4.0.tar.gz
urllib3-1.12.tar.gz
elasticsearch-py-1.8.0.tar.gz
My command and error is as below
**pip install elasticsearch-curator-3.4.0.tar.gz --no-index --find-links=/installdir/ELK/curator/elasticsearch-py-1.8.0.tar.gz**
> Ignoring indexes: [Simple index](https://pypi.python.org/simple/)
> Unpacking ./elasticsearch-curator-3.4.0.tar.gz
> Running setup.py egg\_info for package from file:///installdir/ELK/curator/elasticsearch-curator-3.4.0.tar.gz
> warning: no previously-included files matching ' **pycache**' found under directory '_'
> warning: no previously-included files matching '_.py[co]' found under directory '_'
> warning: no previously-included files matching '_.pyc' found under directory 'docs'
> warning: no previously-included files matching '_.pyo' found under directory 'docs'
> warning: no previously-included files matching '_.pyc' found under directory 'test'
> warning: no previously-included files matching '\*.pyo' found under directory 'test'
> no previously-included directories found matching 'docs/\_build'
> no previously-included directories found matching 'docs/asciidoc/html\_docs'
> Downloading/unpacking elasticsearch\>=1.8.0,\<2.1.0 (from elasticsearch-curator==3.4.0)
> Could not find a version that satisfies the requirement elasticsearch\>=1.8.0,\<2.1.0 (from elasticsearch-curator==3.4.0) (from versions: py-1.8.0, py-1.8.0)
> No distributions matching the version for elasticsearch\>=1.8.0,\<2.1.0 (from elasticsearch-curator==3.4.0)
> Storing complete log in /root/.pip/pip.log
---
### Author:  [@NiteshBarnwal](https://discuss.elastic.co/u/NiteshBarnwal)
#### Post date: [December 21, 2015, 9:43pm UTC](https://discuss.elastic.co/t/issue-while-installing-curator/37714/2 "2015-12-21T21:43:55Z")
installation issue resolved.
Further.
I have deleted the index by using below command
`curator show indices --prefix hello`
Still I am seeing the indices is present at `elasticsearch-1.7.2/data/elasticsearch/nodes/1/indices location`
If the data is not getting deleted, how it will vacate the space. Please help as the system is filling gradually.
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [December 21, 2015, 10:00pm UTC](https://discuss.elastic.co/t/issue-while-installing-curator/37714/3 "2015-12-21T22:00:56Z")
> [@NiteshBarnwal](#):
>
> I have deleted the index by using below command
> `curator show indices --prefix hello`
This will only _show_ indices, not _delete_ them. Perhaps you meant to run:
`curator delete indices --prefix hello`
> [@NiteshBarnwal](#):
>
> Still I am seeing the indices is present at `elasticsearch-1.7.2/data/elasticsearch/nodes/1/indices location`
If you are still seeing this after a successful `delete` command, it could be that the cluster is still catching up and is deleting shards slowly due to I/O restrictions. If the `show` command does not list the index you just deleted, the index data should eventually be deleted.
---
### Author:  [@NiteshBarnwal](https://discuss.elastic.co/u/NiteshBarnwal)
#### Post date: [December 22, 2015, 11:06am UTC](https://discuss.elastic.co/t/issue-while-installing-curator/37714/4 "2015-12-22T11:06:34Z")
my bad for the typo. I ran the delete command.
> [@theuntergeek](#):
>
> it could be that the cluster is still catching up and is deleting shards slowly due to I/O restrictions
yes the indices are not coming in `show` command. Its been more than 13 hours and it is still showing at `elasticsearch-1.7.2/data/elasticsearch/nodes/1/indices` location
Is there any way to clear the cache without restarting.?
can we delete the indices by `rm` command will there be any impact?
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [January 4, 2016, 1:29pm UTC](https://discuss.elastic.co/t/issue-while-installing-curator/37714/5 "2016-01-04T13:29:18Z")
This is a bad thing. This condition should never happen. It almost sounds like a split-brain scenario where one master thinks it should be deleted and another doesn't. You may not have a split-brain, but this is acting like one.
You should _never_ have to manually delete a shard from a file system. That it still seems to exist after a delete, and is not reported by a `show` command is cause for much deeper digging into the cluster state.
---
### Author:  [@NiteshBarnwal](https://discuss.elastic.co/u/NiteshBarnwal)
#### Post date: [January 4, 2016, 5:41pm UTC](https://discuss.elastic.co/t/issue-while-installing-curator/37714/6 "2016-01-04T17:41:42Z")
Hello Aaron, Now the curator is working fine. The only `.marvel.xx.xx.log` is taking space which is hidden. Hence `older-than` parameter worked.
One more question: if elasticsearch is down and I use curator to delete the indices. The deleted indices comes-up again when elasticsearch is started. Is there anyway to change this behaviour?
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [January 4, 2016, 6:14pm UTC](https://discuss.elastic.co/t/issue-while-installing-curator/37714/7 "2016-01-04T18:14:37Z")
Curator is only a front-end to the Elasticsearch API. If Elasticsearch is down, Curator cannot be used, as the API could not be used either.
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [January 4, 2016, 6:15pm UTC](https://discuss.elastic.co/t/issue-while-installing-curator/37714/8 "2016-01-04T18:15:55Z")
> [@NiteshBarnwal](#):
>
> only .marvel.xx.xx.log is taking space which is hidden
Curator can act on these "hidden" indices just fine by using `--prefix .marvel` in the index selection parameters.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:27pm UTC](https://discuss.elastic.co/t/issue-while-installing-curator/37714/9 "2017-07-05T23:27:16Z")