Project

General

Profile

Actions

Bug #6988

closed

pg query doesn't show current 'problem' stats

Added by Dan Mick over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
% Done:

100%

Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

pg <pgid> query shows 0 for the four stats

num_objects_missing_on_primary
num_object_copies
num_objects_unfound
num_objects_degraded

Unfortunately, these are some of the more important items in pg query output when diagnosing problem pgs.

The problem doesn't affect pg dump_stuck, I believe because dump_stuck searches
PGMap and finds PGs in a particular state, then gets the stats from PGMap::pg_stat.
pg <pgid> query, on the other hand, starts from PG::info.stats, which is not
kept up to date.

Sage suggests updating info.stats on the query command, if I understand correctly.

Actions #1

Updated by Sage Weil over 10 years ago

  • Status changed from New to Fix Under Review
Actions #3

Updated by Loïc Dachary over 10 years ago

  • Status changed from Fix Under Review to Resolved
  • Assignee set to Sage Weil
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF