[SERVER-29730] Analyze metadata commands to determine possible concurrency Created: 19/Jun/17 Updated: 29/Jan/18 Resolved: 21/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jessica Yu | Assignee: | Jessica Yu |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2017-07-10 |
| Participants: |
| Description |
|
Look into distributed locks taken by metadata commands, and determine by analyzing their logic how this locking scheme can be improved. |
| Comments |
| Comment by Jessica Yu [ 19/Jun/17 ] |
|
Spreadsheet of locking scheme and command summaries: https://docs.google.com/a/10gen.com/spreadsheets/d/1SVl0Q_N6Lna-iDlMtBOKbM81rWFPJrxrIxoduqIBQDg/edit?usp=sharing |