# More about recovery process detail

**URL:** <https://discuss.elastic.co/t/more-about-recovery-process-detail/110533>\
**Category:** Elasticsearch\
**Created:** [December 6, 2017, 3:01pm UTC](https://discuss.elastic.co/t/more-about-recovery-process-detail/110533 "2017-12-06T15:01:34Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ginger](https://avatars.discourse-cdn.com/v4/letter/g/34f0e0/32.png) [@ginger](https://discuss.elastic.co/u/ginger)\
**Post date:** [December 6, 2017, 3:01pm UTC](https://discuss.elastic.co/t/more-about-recovery-process-detail/110533/1 "2017-12-06T15:01:34Z")

</div>

Hi, all.

I want to learn more about the remote recovery process in ES 5.x. Through reading code, the recovery process is as following: phase1(index)-\>phase2(translog)-\>finalizeRecovery. As far as I know, operations is still allowed when doing phase2. I wonder that how those operations catch up?

Any help would be apprecicated!

---

<div class="post-metadata">

**Author:** ![ginger](https://avatars.discourse-cdn.com/v4/letter/g/34f0e0/32.png) [@ginger](https://discuss.elastic.co/u/ginger)\
**Post date:** [December 8, 2017, 12:42pm UTC](https://discuss.elastic.co/t/more-about-recovery-process-detail/110533/2 "2017-12-08T12:42:25Z")

</div>

mark

---

<div class="post-metadata">

**Author:** ![ginger](https://avatars.discourse-cdn.com/v4/letter/g/34f0e0/32.png) [@ginger](https://discuss.elastic.co/u/ginger)\
**Post date:** [December 11, 2017, 11:41am UTC](https://discuss.elastic.co/t/more-about-recovery-process-detail/110533/3 "2017-12-11T11:41:15Z")

</div>

any help?

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [December 11, 2017, 5:43pm UTC](https://discuss.elastic.co/t/more-about-recovery-process-detail/110533/4 "2017-12-11T17:43:50Z")

</div>

Those operations are sent to the recovering replica too. There's a careful dance done during recovery to ensure that the recovering replica does not miss any operations.

---

<div class="post-metadata">

**Author:** ![ginger](https://avatars.discourse-cdn.com/v4/letter/g/34f0e0/32.png) [@ginger](https://discuss.elastic.co/u/ginger)\
**Post date:** [December 12, 2017, 5:23am UTC](https://discuss.elastic.co/t/more-about-recovery-process-detail/110533/5 "2017-12-12T05:23:13Z")

</div>

Thank jasontedor very much for reply 🙂

Any document or guidance about this?

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [December 12, 2017, 11:28am UTC](https://discuss.elastic.co/t/more-about-recovery-process-detail/110533/6 "2017-12-12T11:28:25Z")

</div>

At this time there is not, the code is the one true source. We _might_ write down a formally-verified model of this component of the system someday, but have much higher priority problems to solve right now.

---

<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:** [January 9, 2018, 11:28am UTC](https://discuss.elastic.co/t/more-about-recovery-process-detail/110533/7 "2018-01-09T11:28:57Z")

</div>

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