[SERVER-40982] Add counters for aborted migrations from lock timeouts Created: 03/May/19 Updated: 29/Oct/23 Resolved: 20/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2019-05-20, Sharding 2019-06-03 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
Add counters for migrations aborting from lock timeouts as described in this section of the diagnostics scope. These counters should be added to the existing "shardingStatistics" serverStatus section on mongoD. |
| Comments |
| Comment by Githook User [ 22/May/19 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |
| Comment by Jack Mulrow [ 20/May/19 ] |
|
Note that after discussion in the code review only one counter was added that tracks the number of migrations aborting from a lock timeout at any point, instead of separate counters for timeouts transitioning between different migration phases. The scope for this project was updated to reflect this. |
| Comment by Githook User [ 20/May/19 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |