RECOVERING state and requires manual intervention - three nodes

Ops and Admin Replication
1

In mongo document ,
https:// www.mongodb.com/docs/manual/reference/replica-states/#mongodb-replstate-replstate.RECOVERING

It mentions:
When this happens, the member enters the RECOVERING state and requires manual intervention.

My case:
I have three node in cluster for mongo ,and one node is in recovering mode, may I know how to fix it by manual intervention ?

tea-prd-rs [direct: other] test> db.printReplicationInfo()
actual oplog size
‘2017.4760961532593 MB’

configured oplog size
‘2016.07373046875 MB’

log length start to end
‘69830.99999904633 secs (19.4 hrs)’

oplog first event time
‘Mon Jul 24 2023 16:55:17 GMT+0000 (Coordinated Universal Time)’

oplog last event time
‘Tue Jul 25 2023 12:19:08 GMT+0000 (Coordinated Universal Time)’

now
‘Thu Sep 14 2023 07:44:06 GMT+0000 (Coordinated Universal Time)’

Thanks.

2

A member transitions from RECOVERING to SECONDARY after replicating enough data to guarantee a consistent view of the data for client reads.

and

Due to overload, a secondary may fall far enough behind the other members of the replica set such that it may need to resync with the rest of the set. When this happens, the member enters the RECOVERING state and requires manual intervention.

so you need to understand which case this is. if it’s still catching up with primary, then no manual work needed. Otherwise it is already falling behind and the oplog entries on primary are already gone. In that case do the resync.