Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-8096

--fastsync should be prohibited on a replica set

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.3.2
    • Fix Version/s: 2.4.0-rc0
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      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

        Attachments

        1. fastsync_tyler.js
          1 kB
        2. fastsync_tyler.js
          1 kB

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: