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

MongoS can't be shut down for at least 1.5 minutes if a legacy config server is unreachable

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 3.2.0
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The legacy catalog manager initialization code sleeps for 10 seconds and then retries, if a config server host cannot be reached. This may delay shutdown of MongoS or MongoD by at least 1.5 minutes, because it ignores the isShutdown bit.

      This always happens with MongoS, but on MongoD only happens in the presence of minOpTime recovery information, because SERVER-21222.

      We should make it check for the isShutdown bit.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: