Project

General

Profile

Actions

Bug #15686

closed

reweight-by-utilization:- While increasing the weight of the underutilized osds we should consider the least used first

Added by Shylesh Kumar almost 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
jewel, hammer
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

reweight-by-utilization command along with the decreasing the overutilized osds it will also increase the weight of underutilized, But while choosing the underutilized there is a small glitch reweight-by-utilization works on a sorted list from higher to lower utilized osds.

for ex assume utilization list looks like [0.80, 0.75,0.71, 0.60, 0.55,0.45,0.30] and assume avg_utilization=0.60 and max_osd=4. Now assume there are 2 osds which satisfy oload values and it will be picked for decreasing the weight, since max_osd is 4 we can choose 2 more osds for increasing the weight.

While walking in this list first osd with utilization of 0.55(which is less than 0.60) will be considered as underutilized and thereby its weight will be increased. Instead we can pick the osd with 0.30 utilization since its the most underutilized osd.


Related issues 2 (0 open2 closed)

Copied to Ceph - Backport #15769: jewel: reweight-by-utilization:- While increasing the weight of the underutilized osds we should consider the least used firstResolvedSage WeilActions
Copied to Ceph - Backport #15770: hammer: reweight-by-utilization:- While increasing the weight of the underutilized osds we should consider the least used firstResolvedJesse WilliamsonActions
Actions

Also available in: Atom PDF