Project

General

Profile

Documentation #41004

doc: pg_num should always be a power of two

Added by Kai Wagner 25 days ago. Updated 25 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
07/30/2019
Due date:
% Done:

0%

Tags:
Backport:
nautilus
Reviewed:
Affected Versions:
Pull request ID:

Description

Hi,

I updated the pg_num section in the docs just a little to be more strict.
I think we should make it crystal clear that pg num should be a power of two and only if there's a real good reason and someone knows exactly why they need a different value they can proceed.

I think this is the first step of several to make this clearer to the end user. Next step would be to show a Health WARN and also to flag the pool creation red in the dashboard if someone would like to add a pool and the pg count isn't a power of two.

Why do I would like to be more strict about it? We've seen more and more clusters were the osd variation was really high. The fix to that was always to set the pg_num + balancer. Also the pg autoscaler only uses power of two so we shouldn't even encourage people to use something different right from the beginning or to phrase i differently, we should protect the end-user right away.


Related issues

Related to mgr - Feature #40983: mgr/dashboard: Warn when setting pg_num to not-a-power-of-two Rejected 07/26/2019

History

#2 Updated by Sebastian Wagner 25 days ago

  • Related to Feature #40983: mgr/dashboard: Warn when setting pg_num to not-a-power-of-two added

#3 Updated by Sebastian Wagner 25 days ago

  • Project changed from Ceph to RADOS
  • Category deleted (documentation)
  • Status changed from New to In Progress
  • Pull request ID set to 29364

Also available in: Atom PDF