[SERVER-18469] Improve naming of secs_running / microsecs_running Created: 14/May/15  Updated: 03/Feb/16  Resolved: 17/Nov/15

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Kevin Pulo Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: curop, currentop
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-18470 Give some indication of age of inacti... Backlog
Participants:

 Description   

In currentOp output, the "secs_running" and "microsecs_running" field names are somewhat misleading. They are actually the number of secs/microsecs since the operation started. The connotation of "_running" is that the operation has been actively running for all of this time, but that might not be the case.

Better would be something like "(micro)secs_elapsed" or "(micro)secs_since_start".

Unfortunately straight out renaming the fields is likely to be impossible due to breaking backwards compatibility.



 Comments   
Comment by Ian Whalen (Inactive) [ 17/Nov/15 ]

as discussed in the description, this is currently not going to happen given that it will break backwards compatibility.

Generated at Thu Feb 08 03:47:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.