# Is it necessary to add a quick recovery configuration item like "indices.recovery.fast"

**URL:** https://discuss.elastic.co/t/is-it-necessary-to-add-a-quick-recovery-configuration-item-like-indices-recovery-fast/83491
**Category:** Elasticsearch
**Created:** [April 25, 2017, 4:58am UTC](https://discuss.elastic.co/t/is-it-necessary-to-add-a-quick-recovery-configuration-item-like-indices-recovery-fast/83491 "2017-04-25T04:58:54Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![johnyannj](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@johnyannj](https://discuss.elastic.co/u/johnyannj)
#### Post date: [April 25, 2017, 4:58am UTC](https://discuss.elastic.co/t/is-it-necessary-to-add-a-quick-recovery-configuration-item-like-indices-recovery-fast/83491/1 "2017-04-25T04:58:54Z")

</div>

when shard become very large, restart one cluster will waste too much time,

I know the primary shard become started is very fast.

but the cluster become green from yellow is very slow, become replica shard need recovery：

Especially the first phase of recovery.

Sometimes we need fast recovery services, not too concerned about data consistency。

I recommend adding a configuration item: “indices.recovery.fast”， which can be dynamically modified。

Then we can skip first phase of recovery~~

org.elasticsearch.indices.recovery.RecoverySourceHandler

```
public void phase1(final SnapshotIndexCommit snapshot) throws ElasticsearchException{
.....
//add one fast recovery branch
if (recoverySettings.fast() && !request.markAsRelocated()) {
......
            
 } else if (recoverWithSyncId) {
         
......
 } else {

......
}
```

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [April 25, 2017, 6:11am UTC](https://discuss.elastic.co/t/is-it-necessary-to-add-a-quick-recovery-configuration-item-like-indices-recovery-fast/83491/2 "2017-04-25T06:11:56Z")

</div>

For the record, same thread also opened at

> <https://github.com/elastic/elasticsearch/issues/24302>

---

<div class="post-metadata">

### Author: ![johnyannj](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@johnyannj](https://discuss.elastic.co/u/johnyannj)
#### Post date: [April 25, 2017, 12:17pm UTC](https://discuss.elastic.co/t/is-it-necessary-to-add-a-quick-recovery-configuration-item-like-indices-recovery-fast/83491/3 "2017-04-25T12:17:04Z")

</div>

but it is closed by @ywelsch  
I think many people require this feature~~~

---

<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: [May 23, 2017, 12:29pm UTC](https://discuss.elastic.co/t/is-it-necessary-to-add-a-quick-recovery-configuration-item-like-indices-recovery-fast/83491/4 "2017-05-23T12:29:08Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.