[SERVER-61078] Log chunk migration donor critical section times as attr.durationMillis Created: 28/Oct/21 Updated: 29/Oct/23 Resolved: 06/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Enrico Golfieri |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding EMEA 2022-04-18 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently the migration donor critical section times are reported in serverStatus.shardingStatistics as a total cumulative time.. It could be useful to also report it (individually for each critical section, instead of cumulative) in a log line with a attr.durationMillis attribute. |
| Comments |
| Comment by Githook User [ 06/Apr/22 ] |
|
Author: {'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}Message: |
| Comment by Jordi Serra Torrens [ 11/Jan/22 ] |
It is indeed logged there as one of the steps. This ticket came from this suggestion to also log the critical section time as a 'attr.durationMillis', which seems to be the most standard format. |
| Comment by Sergi Mateo Bellido [ 11/Jan/22 ] |
|
Aren't we already logging this information through the MoveTimeHelper object? |