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

Warn if network RTT to any config server is (relatively) high

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • Sharding

    Description

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

      For the config database with a large number of chunks (100k), the upgrade process can take many many hours (6+) when latency to one of the config servers is seconds. (We have seen it take 30-40 min all config servers are within milliseconds ping with that large number of chunks)

      We should be able to display a warning (esp. during the upgrade process) if we detect that ping time to the config servers, or any config server relative to the other(s), is too high.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            alex.komyagin@mongodb.com Alexander Komyagin
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: