Actions
Bug #39570
closednautilus with requrie_osd_release < nautilus cannot increase pg_num
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
On Mon, 29 Apr 2019, Alexander Y. Fomichev wrote:
Hi,
I just upgraded from mimic to nautilus(14.2.0) and stumbled upon a strange
"feature".
I tried to increase pg_num for a pool. There was no errors but also no
visible effect:until finally I found that
- ceph osd pool get foo_pool01 pg_num
pg_num: 256- ceph osd pool set foo_pool01 pg_num 512
set pool 11 pg_num to 512- ceph osd pool get foo_pool01 pg_num
pg_num: 256
- ceph osd require-osd-release nautilus
solves this problemDocs are very scarce about "require-osd-release" command. Something like
"Complete the upgrade by disallowing pre-Nautilus OSDs and enabling all new
Nautilus-only functionality:" which gives no clue to understand why pretty
old feature of increasing pg_num dosn't work. Any way I doubt that silently
ignoring user commands is a good idea.
So question is: It is intentional behavior or I hit a bug.
mon sets pg_num_target but encodes with mimic features.
Updated by Sage Weil almost 5 years ago
- Status changed from In Progress to Fix Under Review
Updated by Neha Ojha almost 5 years ago
- Project changed from Ceph to RADOS
- Status changed from Fix Under Review to Pending Backport
Updated by Josh Durgin almost 5 years ago
- Has duplicate Bug #40193: Changing pg_num and other pool settings are ignored added
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40322: nautilus: nautilus with requrie_osd_release < nautilus cannot increase pg_num added
Updated by Greg Farnum over 4 years ago
- Status changed from Pending Backport to Resolved
Actions