Project

General

Profile

Feature #36187

Crush rule ssd-primary should take previous emit result into consideration

Added by Horace Ng almost 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Component(RADOS):
Pull request ID:

Description

http://docs.ceph.com/docs/master/rados/operations/crush-map-edits/
The document entry "PLACING DIFFERENT POOLS ON DIFFERENT OSDS:" is a not yet implemented feature for the "rule ssd-primary".

The ssd-primary is not taking previous emit into consideration, hence a SSD member and a SATA member from the same PG may still store in the same host.

The new version of rule using device class also returns the same result.

rule ssd-primary {
id 2
type replicated
min_size 1
max_size 10
step take default class ssd
step chooseleaf firstn 1 type host
step emit
step take default class hdd
step chooseleaf firstn -1 type host
step emit
}

More details on a bug request https://tracker.ceph.com/issues/24264#change-114715 but it has been closed.

History

#1 Updated by Greg Farnum almost 2 years ago

  • Tracker changed from Bug to Feature
  • Project changed from Ceph to RADOS

Also available in: Atom PDF