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

onShardVersionMismatch must catch exceptions in AutoGetCollection

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Sharding
    • None
    • Sharding
    • ALL

      onShardVersionMismatch in src/mongo/db/s/shard_filtering_metadata_refresh.cpp is marked noexcept, meaning any exception which escapes the context will terminate the server. AutoGetCollection can throw an exception if it can't get the collection lock for any reason, including step down. So a badly timed step down crashes the process.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: