[SERVER-16091] Revisit mongo::Client/mongo::CurOp thread-safety Created: 11/Nov/14 Updated: 16/Nov/16 Resolved: 16/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | David Storch |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
The way concurrency is achieved for the various fields of mongo::Client is a bit strange. Some fields use a SpinLock (such as CurOp) and some use the clientsMutex. |
| Comments |
| Comment by David Storch [ 16/Nov/16 ] |
|
Since this ticket was filed, we have put work into cleaning up concurrency control around Client and CurOp. Closing as Won't Fix. |