-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Minor - P4
-
None
-
Affects Version/s: 1.9.2
-
Component/s: Replication, Usability
-
Replication
If "too stale to catch up" means it will never catch up then I think this deserves a different state besides RECOVERING, which implies it will catch up eventually. Maybe the new state should be STALE indicating to the user that he will need to resync it.
- is depended on by
-
TOOLS-45 MongoStat does not indicate if replica is STALE
- Closed
- related to
-
SERVER-1933 "too stale to catch up" leaves state as 2
- Closed