[SERVER-37964] Track the wall clock time when an index build begins Created: 06/Nov/18 Updated: 29/Oct/23 Resolved: 10/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Benety Goh |
| 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: | Storage NYC 2018-12-17 | ||||||||
| Participants: | |||||||||
| Description |
|
We want to report how long an index build has been running in order to report it in currentOp output. I'm not sure what behavior we want if a mongod restarts, whether to restart the start time or persist the start time so that it can be found on startup. This needs to be explored, possibly with Cloud people. |
| Comments |
| Comment by Benety Goh [ 10/Dec/18 ] | ||||||||
|
We added the call to CurOp::ensureStarted() in | ||||||||
| Comment by Benety Goh [ 05/Dec/18 ] | ||||||||
|
Using CurOp::ensureStarted() to add the secs_running and microsecs_running fields to the CurOp output might be sufficient to satisfy the goals of this ticket: Sample output:
|