Project

General

Profile

Actions

Bug #12025

closed

rados mkpool/ pool_create should warn/error when pgp_num > pg_num

Added by Abhishek Lekshmanan almost 9 years ago. Updated about 8 years ago.

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

0%

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

Description

Ran into a wierd case when our configuration management utility had only set ceph_osd_default_pgp_num to a non default value. Since ceph_osd_default_pg_num was still the default of 8; when either creating a pool with rados mkpool or when radosgw started (which in turn creates pools with rados::create_pool) we ran into issues like misdirected client requests, which after a lot of looking at wrong places was finally found out when doing a ceph osd dump

This can be reproduced by setting doing something like

 sudo ceph tell mon.ceph injectargs --osd_pool_default_pgp_num 256

and then creating pool with rados

$ rados mkpool broken_pool
$ ceph osd pool get broken_pool pg_num
pg_num: 8
$ sudo ceph osd pool get broken_pool pgp_num
pgp_num: 256

While ceph osd pool create explicitly catches when setting a pgp_num > pg_num it would be nice if rados mkpool/ pool create had some guard to prevent this from happening

Actions #1

Updated by Xinxin Shu almost 9 years ago

  • Status changed from New to 12
Actions #2

Updated by Xinxin Shu almost 9 years ago

  • Assignee set to Xinxin Shu
Actions #3

Updated by Kefu Chai almost 9 years ago

  • Status changed from 12 to Fix Under Review
Actions #4

Updated by Abhishek Lekshmanan about 8 years ago

  • Status changed from Fix Under Review to Resolved

PR Merged into master

Actions

Also available in: Atom PDF