[SERVER-55283] Clean up unnecessary mutex acquisitions in tenant migration recipient service Created: 17/Mar/21 Updated: 06/Dec/22 Resolved: 25/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
We do not need to hold the tenant migration recipient service mutex while reading the state doc in the main chain. It should be impossible for another thread to be changing _stateDoc. reportForCurrentOp requires the mutex before reading the _stateDoc because the operation comes from a user thread. |
| Comments |
| Comment by Lingzhi Deng [ 25/Jun/21 ] |
|
Moving this out of PM-2139 and closing as "Won't fix" until whenever we actually need it. |