# Replica pod is in archive recovery state from long time

**URL:** <https://forums.percona.com/t/replica-pod-is-in-archive-recovery-state-from-long-time/31983>\
**Category:** Percona Operator for PostgreSQL\
**Created:** [August 2, 2024, 3:18pm UTC](https://forums.percona.com/t/replica-pod-is-in-archive-recovery-state-from-long-time/31983 "2024-08-02T15:18:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ramesh\_Raju\_HP](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ramesh_raju_hp/32/14161_2.png) [@Ramesh\_Raju\_HP](https://forums.percona.com/u/Ramesh_Raju_HP)\
**Post date:** [August 2, 2024, 3:18pm UTC](https://forums.percona.com/t/replica-pod-is-in-archive-recovery-state-from-long-time/31983/1 "2024-08-02T15:18:50Z")

</div>

## Description:

The replica pod is “in archive recovery state from long time”

- 

| Member | Host | Role | State | TL | Lag in MB |  
±--------------------------±-----------------------------------------------±--------±--------------------±—±----------+  
| cluster-rs-7n5b-0 | cluster-rs-7n5b-0.cluster-pods | Replica | in archive recovery | 8 | 288 |  
| cluster-rs-bdtz-0 | cluster-rs-bdtz-0.cluster-pods | Leader | running | 8 | |  
±--------------------------±-----------------------------------------------±--------±--------------------±—±----------

What should I do to decrease the lag?