# Quicker recovery?

**URL:** <https://discuss.elastic.co/t/quicker-recovery/7169>\
**Category:** Elasticsearch\
**Created:** [March 28, 2012, 7:10pm UTC](https://discuss.elastic.co/t/quicker-recovery/7169 "2012-03-28T19:10:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacque74](https://avatars.discourse-cdn.com/v4/letter/j/4af34b/32.png) [@jacque74](https://discuss.elastic.co/u/jacque74)\
**Post date:** [March 28, 2012, 7:10pm UTC](https://discuss.elastic.co/t/quicker-recovery/7169/1 "2012-03-28T19:10:54Z")

</div>

Hello, I have a situation when I need to shutdown a node, and then  
start it up after 5 minutes. The node is a datanode, what I see is  
that after the startup the datanode will basically wait for the  
cluster to become green without recovering any of its local shards  
first. This causes excessive replication, then rebalancing when  
cluster is green back to the node that has started, so we end up  
rewriting data (slushing) several times. How can I tune my cluster to  
have a restarted datanode start local recovery right away?

-Jack

---

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [March 28, 2012, 7:32pm UTC](https://discuss.elastic.co/t/quicker-recovery/7169/2 "2012-03-28T19:32:10Z")

</div>

Hi Jack,

Have a look at this thread:

> **[Google Groups](https://groups.google.com/access-error?continue=https:%2F%2Fgroups.google.com%2Fg%2Felasticsearch%2Fc%2FiyWxQaF-FGU%2Fm%2F9nToZElZu2YJ)**

## Otis

Hiring Elasticsearch Consultants -

> **[Jobs](https://sematext.com/jobs/)**
>
> We’re Hiring We are always looking for smart, passionate, motivated, and independent people regardless of where on the planet they may be. Learn more about the company Agent & Backend Engineer Full Stack Developer Backend Engineer Frontend...

On Thursday, March 29, 2012 3:10:54 AM UTC+8, Jack Levin wrote:

> Hello, I have a situation when I need to shutdown a node, and then  
> start it up after 5 minutes. The node is a datanode, what I see is  
> that after the startup the datanode will basically wait for the  
> cluster to become green without recovering any of its local shards  
> first. This causes excessive replication, then rebalancing when  
> cluster is green back to the node that has started, so we end up  
> rewriting data (slushing) several times. How can I tune my cluster to  
> have a restarted datanode start local recovery right away?
> 
> -Jack

---

<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:34am UTC](https://discuss.elastic.co/t/quicker-recovery/7169/3 "2017-07-06T03:34:15Z")

</div>

Closed on July 6, 2017, 3:34am UTC