Authentication database should be synced first during an initial sync

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.4.14, 3.5.10
    • Affects Version/s: 3.0.13, 3.2.7, 3.4.0
    • Component/s: Replication
    • Fully Compatible
    • ALL
    • v3.4
    • Repl 2017-06-19, Repl 2017-07-10
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      During an initial sync it is not possible to connect and therefore, collect any monitoring data as per authentication issues. Please note that the initial sync for big volumes of data can take many days.

      It seems like the initial sync process should sync the admin database first. The code change occurred as part of SERVER-17671 and is included in 3.0.2 and later.

      However, at that code, the "fetching and creating collections" stage runs on a list where "admin" has been moved to the first element. But that database name gets inserted into a lexicographically sorted map, which is used to invoke the "initial sync cloning db" stage. "activities" sorts before "admin" so gets cloned first.

            Assignee:
            Jason Chan
            Reporter:
            Ricardo Lorenzo (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: