So if I understand it correct, the final values for PGs should be like below-
>5 && <=10 512
>10 && <=20 1024
>20 && <=30 2048
>30 && <=40 3072
>40 && <=50 4096
>50 Use the formula to calculate PGs
Is this understanding correct and should we go ahead and implement this?
Sam, can you please confirm the above comment#2.
If this understanding is correct?
osds pgs size 2 size 3
5 128 76 51
6 512 256 170
10 512 153 102
11 1024 279 186
20 1024 153 102
21 2048 292 195
30 2048 204 136
31 3072 297 198
40 3072 230 153
41 4096 299 199
50 4096 245 163
With replication set to 2, these numbers work pretty well (between 100 and 200). With replication set to 3, it's a little on the high side, but still between 150 and 300. That's probably ok if we need to use the same guideline for both. 300 pgs/osd is on the high side, but not horrible.
So looks like the logic in comment#2 looks good. I would go ahead with this.
Thanks Sam for explanation.
As confirmed in comment#5 below changes would be done for this issue
1. Update backend logic to calculate the pg nums as per comment#2
2. Update UI slider logic to adhere to logic in comment#2
Fixed as per comments 2, 3 in https://bugzilla.redhat.com/show_bug.cgi?id=1375538
What is the final resolution of this Bug?
Accordingly to comment 5, there should be some update in the logic for automatic PG calculation, but accordingly to Comment 7 (pointing to Bug 1375538 comment 2 and 3), the automatic calculation should be completely removed.
Daniel, as per latest discussions with Michael Kidd, we no more would do auto calculation of PG nums and there is a text box provided in UI to admin to enter the value. Also there would be a link provided to PG Calc tool in UI.
Refer https://bugzilla.redhat.com/show_bug.cgi?id=1375538 for more details on this decision.
I'm verifying this bug, as per comment 10, the PG calculation logic was completely removed and there is just box to set manually the number of PGs. Additional details related to the change will be verified in bug 1375538.
Red Hat Enterprise Linux Server release 7.3 (Maipo)
Doc-text looks good.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.