Actions
Feature #18468
closedDisallow enabling 'hashpspool' option to a pool without some kind of --i-understand-this-will-remap-all-pgs flag
% Done:
0%
Source:
Support
Tags:
Backport:
jewel
Reviewed:
Affected Versions:
Pull request ID:
Description
- Disallow enabling 'hashpspool' option to a pool without some kind of --i-understand-this-will-remap-all-pgs flag
Some users have clusters which were created during bobtail release
and at that time this option 'hashpspool' was not present.
We need this flag because if any user enables 'hashpspool' option on a pool,
it will change the way in which PGs in that pool are hashed(it will basically remap every pg in the pool)
and then the data movement would be catastrophic.
Other than pg hashing for the way pool/pg overlap works there are no other benefits
and for a production cluster which has a large number of osds and a large amount of data
enabling this option is surely not recommended at all.
Updated by Vikhyat Umrao over 7 years ago
Updated by Vikhyat Umrao about 7 years ago
- Status changed from New to Fix Under Review
- Backport set to jewel
- Release set to jewel
Updated by Kefu Chai about 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Loïc Dachary about 7 years ago
- Copied to Backport #18959: jewel: Disallow enabling 'hashpspool' option to a pool without some kind of --i-understand-this-will-remap-all-pgs flag added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions