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

Create a mutex in RoutingTableHistory to protect access to the ShardVersionMap.

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None

    Description

      Feature Work

      This mutex will only be used when accessing or changing the not-yet-created mutable shardVersions map. We don’t need it yet, but to shake out any potential bugs, place the mutex around all accesses of the current ShardVersionMap that exist on the RoutingTableHistory.

      Testing Work

      We won’t add additional tests for this step — we just want to make sure that read accesses don’t case deadlocks, so Evergreen will be sufficient.

      Attachments

        Activity

          People

            blake.oler@mongodb.com Blake Oler
            blake.oler@mongodb.com Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: