[SERVER-16825] Use LocksType to parse config.locks documents Created: 13/Jan/15 Updated: 29/Dec/16 Resolved: 25/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.8.0-rc4 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Randolph Tan | Assignee: | Daniel Alabi |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2 04/24/15, Sharding 3 05/15/15, Sharding 4 06/05/15, Sharding 5 06/26/16 | ||||||||
| Participants: | |||||||||
| Description |
|
This should make the error messages clearer when reading malformed lock documents (instead of the "Assertion: 13111:field not found, expected type 7" error). |
| Comments |
| Comment by Randolph Tan [ 08/Jun/15 ] |
|
Lowering priority since the legacy distributed lock code is going to be phased out soon. |