# Problem with Elastic Search cluster

**URL:** <https://discuss.elastic.co/t/problem-with-elastic-search-cluster/6956>\
**Category:** Elasticsearch\
**Created:** [March 9, 2012, 8:18am UTC](https://discuss.elastic.co/t/problem-with-elastic-search-cluster/6956 "2012-03-09T08:18:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vibin](https://avatars.discourse-cdn.com/v4/letter/v/2bfe46/32.png) [@vibin](https://discuss.elastic.co/u/vibin)\
**Post date:** [March 9, 2012, 8:18am UTC](https://discuss.elastic.co/t/problem-with-elastic-search-cluster/6956/1 "2012-03-09T08:18:03Z")

</div>

Hi,

I have Elastic Search server with two cluster nodes,

You can find Elastic Search cluster configuration file here

> <https://gist.github.com/Manokrrish/2005573>

It handles 20 GB data per day. Due to insufficient memory I suppose to  
delete some of old index folders from both the nodes, Unfortunately I  
removed folders from server(Linux) using "rm -rf" command instead of  
"curl -XDELETE" in both the nodes after killing elastic search (Using  
"kill -9"). When I try to start elasticsearch after deletion I got to  
know more than 1 instance of elastic search is running in server(I  
don't know how) and more than 1 shard (It suppose to be 1) in some  
folders, Then I deleted additional shards using "rm -rf" command. When  
I try to index I'm getting the following error and the documents are  
not getting indexed,

UnavailableShardsException[[2012-03-07][0] [2] shardIt, [0] active :  
Timeout waiting for [1m], request:  
org.elasticsearch.action.bulk.BulkShardRequest@7403e02a]

Is there any possibility of recovering the cluster without loss of  
already available data(Currently I'm having 900GB indexed data), If so  
could you please suggest me a solution to resolve this issue?

Thanks,  
Vibin

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [March 9, 2012, 7:03pm UTC](https://discuss.elastic.co/t/problem-with-elastic-search-cluster/6956/2 "2012-03-09T19:03:06Z")

</div>

Delete using the delete API those indices.

On Friday, March 9, 2012 at 10:18 AM, vibin dhas wrote:

> Hi,
> 
> I have Elastic Search server with two cluster nodes,
> 
> You can find Elastic Search cluster configuration file here  
> [my elastic search cluster configuration · GitHub](https://gist.github.com/2005573)
> 
> It handles 20 GB data per day. Due to insufficient memory I suppose to  
> delete some of old index folders from both the nodes, Unfortunately I  
> removed folders from server(Linux) using "rm -rf" command instead of  
> "curl -XDELETE" in both the nodes after killing Elasticsearch (Using  
> "kill -9"). When I try to start elasticsearch after deletion I got to  
> know more than 1 instance of Elasticsearch is running in server(I  
> don't know how) and more than 1 shard (It suppose to be 1) in some  
> folders, Then I deleted additional shards using "rm -rf" command. When  
> I try to index I'm getting the following error and the documents are  
> not getting indexed,
> 
> UnavailableShardsException[[2012-03-07][0] [2] shardIt, [0] active :  
> Timeout waiting for [1m], request:  
> org.elasticsearch.action.bulk.BulkShardRequest@7403e02a]
> 
> Is there any possibility of recovering the cluster without loss of  
> already available data(Currently I'm having 900GB indexed data), If so  
> could you please suggest me a solution to resolve this issue?
> 
> Thanks,  
> Vibin

---

<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:** [July 6, 2017, 3:36am UTC](https://discuss.elastic.co/t/problem-with-elastic-search-cluster/6956/3 "2017-07-06T03:36:31Z")

</div>