Bug #7218: Displaying wrong number of pools with ceph -s after removeing a pool - Ceph - Ceph

Actions

Copy link

Bug #7218

closed

Displaying wrong number of pools with ceph -s after removeing a pool

Added by Sherry Shahbazi over 10 years ago. Updated about 10 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Sherry Shahbazi

Category:

Target version:

% Done:

Source:

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

$ceph osd lspools
0 pool0,1 pool1,2 pool2,3 pool3,
ceph osd pool delete pool0 pool0 --yes-i-really-really-mean-it
$ceph osd lspools
1 pool1,2 pool2,3 pool3,
$ ceph -s
pgmap v1800: 730 pgs, 4 pools,

Actions

Copy link

Updated by Dan Mick over 10 years ago

I looked, and this is reporting a hash_map .size(); I'll bet .size() isn't an accurate count of currently-defined keys, but rather the allocated size

Actions

Copy link

Updated by Greg Farnum over 10 years ago

Where are you looking?

I'm assuming that since this is PGMap output, the OSDs haven't all finished deleting the pool and updating the monitor's stats.

Actions

Copy link

Updated by Dan Mick about 10 years ago

The experiment I did yesterday still shows the inconsistency. I was just looking at the output, in PGMap::print_summary, and assuming what probably happens with hash_map.size(). I don't know. Maybe the issue is that pg_pool_sum is stale, but it hasn't updated itself in nearly a day.

Actions

Copy link