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

Consider running shardRemovalHooks synchronously

    • Type: Icon: Improvement Improvement
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding EMEA

      Currently they are run asynchronously, but this means that multiple copies may run concurrently and race with each other (or with ShardRegistry::_lookup() itself). So it may be better to instead run these callbacks synchronously, if possible.

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: