Actions
Bug #10356
closednew optracker requests show up with bad age
Status:
Rejected
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
{ "ops": [ { "description": "osd_op(client.4894101.1:174810379 10006ae2f1d.00000000 [read 0~4096 [1@-1]] 0.45a765a4 RETRY=1 retry+read e375221)", "initiated_at": "2014-12-16 21:11:04.418307", "age": "48872.086396", "duration": "0.000000", "type_data": [ "no flag points reached", { "client": "client.4894101", "tid": 174810379}, [ { "time": "2014-12-16 21:11:04.418307", "event": "initiated"}]]},
this request wasn't present in the dump ops a few seconds ago and disappeared almost immediately after.
Updated by Sage Weil about 9 years ago
- Status changed from New to Rejected
i think it was stuck for that long (~13 hrs) and just hadn't reached the optracker
Actions