[SERVER-52712] OpDebug should take the Client lock while accessing ClientMetadata Created: 09/Nov/20 Updated: 15/Jun/21 Resolved: 15/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | George Wangensteen |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Service Arch 2021-06-28 | ||||
| Participants: | |||||
| Linked BF Score: | 133 | ||||
| Description |
|
It seems that we do not synchronize the Client while accessing ClientMetadata in OpDebug. With the new implementation of ClientMetadata, this has become apparent as a problem. We should be synchronizing, it is out of line access to Clients. |