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

--fastsync should be prohibited on a replica set

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.4.0-rc0
    • Affects Version/s: 2.3.2
    • Component/s: Replication
    • Labels:
      None
    • ALL

      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

        1. fastsync_tyler.js
          1 kB
          Kristina Chodorow
        2. fastsync_tyler.js
          1 kB
          Tyler Brock

            Assignee:
            kristina Kristina Chodorow (Inactive)
            Reporter:
            tyler@10gen.com Tyler Brock
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: