[SERVER-44499] Create a mutex in RoutingTableHistory to protect access to the ShardVersionMap. Created: 08/Nov/19  Updated: 11/Nov/19  Resolved: 11/Nov/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Blake Oler
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 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.



 Comments   
Comment by Blake Oler [ 11/Nov/19 ]

We decided not to take the approach where we will be creating a new mutex.

Generated at Thu Feb 08 05:06:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.