Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-1899

Comment on: "manual/release-notes/2.4-upgrade.txt"

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 01112017-cleanup
    • None
    • None

    Description

      Since it's somewhat reasonable to place one of the config servers into Disaster Recovery Zone, the metadata upgrade procedure can take a very long time because of the high network latency.

      For the config database with 100000 chunks, the upgrade process can take up to 6 hours when latency to one of the config servers is 1-2 seconds. (it take 30-40 min when all config servers are within milliseconds ping)

      We should put an appropriate note saying that the metadata upgrade duration is highly dependent on the network RTT to all three config servers from the node running the 'mongos --upgrade' to set proper expectations for users.

      Attachments

        Activity

          People

            zack.brown@10gen.com Zack Brown
            alex.komyagin@mongodb.com Alexander Komyagin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              10 years, 22 weeks, 1 day ago