Actions
Bug #40821
closedosdc: objecter ops output does not have useful time information
% Done:
0%
Source:
Development
Tags:
Backport:
nautilus,mimic,luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
$ ceph daemon mds.foo objecter_requests
{
"ops": [
{
"tid": 23023746,
"pg": "2.a1013e54",
"osd": 2,
"object_id": "200.09aacbee",
"object_locator": "@2",
"target_object_id": "200.09aacbee",
"target_object_locator": "@2",
"paused": 0,
"used_replica": 0,
"precalc_pgid": 0,
"last_sent": "2.96351e+07s",
"attempts": 1,
"snapid": "head",
"snap_context": "0=[]",
"mtime": "2019-07-17 11:29:01.0.925253s",
"osd_ops": [
"write 312209~365182 [fadvise_dontneed]"
]
},
...
last_sent is printed in scientific format. I believe it's meant to be a UNIX epoch. Also, the age of the op should be included for easier filtering.
Updated by Varsha Rao over 4 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 29818
Updated by Patrick Donnelly over 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42158: nautilus: osdc: objecter ops output does not have useful time information added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42159: mimic: osdc: objecter ops output does not have useful time information added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42160: luminous: osdc: objecter ops output does not have useful time information added
Updated by Nathan Cutler almost 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions