Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
2.3.2
-
None
-
ALL
Description
If Replica set members are un-initiated and have fastsync enabled, then calling rs.initiate() causes nodes to enter "RECOVERING" state from which they never recover and print the following message continously:
Mon Jan 7 11:21:17.119 [rsSync] replSet initial sync pending
|
Mon Jan 7 11:21:17.119 [rsSync] replSet syncing to: localhost:27017
|
Mon Jan 7 11:21:17.120 [rsSync] fastsync: skipping database clone
|
Mon Jan 7 11:21:17.121 [rsSync] replSet error possible failover clock skew issue? 50eaf54f:1
|
This was not the behavior in 2.3.1 or 2.2.X