MongoDB 集群节点 RECOVERYING 状态解决办法

mongo shard4节点状态：

2018-10-22T11:26:52.664+0800 I REPL     [replication-0] We are too stale to use 172.17.1.75:27013 as a sync source. Blacklisting this sync source because our last fetched timestamp: 5bc9d57a:40 is before their earliest timestamp: 5bcb3e7b:182c for 1min until: 2018-10-22T11:27:52.664+0800
2018-10-22T11:26:52.664+0800 I REPL     [replication-0] could not find member to sync from
2018-10-22T11:26:52.664+0800 E REPL     [rsBackgroundSync] too stale to catch up -- entering maintenance mode
2018-10-22T11:26:52.664+0800 I REPL     [rsBackgroundSync] Our newest OpTime : { ts: Timestamp 1539954042000|64, t: 8 }
2018-10-22T11:26:52.664+0800 I REPL     [rsBackgroundSync] Earliest OpTime available is { ts: Timestamp 1540046459000|6188, t: 53 }

本节点的最后时间戳比同步目标最早的时间戳还要早一分钟；也就是由于一些原因太久没有进行同步数据操作，而导致其他节点的数据操作日志已经覆盖，所以本节点被认为是太陈旧了，无法从其他节点同步数据。

解决：

主要一点记住ÿ