Project

General

Profile

Feature #18468

Disallow enabling 'hashpspool' option to a pool without some kind of --i-understand-this-will-remap-all-pgs flag

Added by Vikhyat Umrao 9 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
01/09/2017
Due date:
% Done:

0%

Source:
Support
Tags:
Backport:
jewel
Reviewed:
User Impact:
Affected Versions:
Release:
jewel
Needs Doc:
No

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.


Related issues

Copied to Ceph - Backport #18959: jewel: Disallow enabling 'hashpspool' option to a pool without some kind of --i-understand-this-will-remap-all-pgs flag Resolved

History

#2 Updated by Vikhyat Umrao 7 months ago

  • Status changed from New to Need Review
  • Backport set to jewel
  • Release jewel added

#3 Updated by Kefu Chai 7 months ago

  • Status changed from Need Review to Pending Backport

#4 Updated by Loic Dachary 7 months 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

#5 Updated by Nathan Cutler about 2 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF