Actions
Feature #8992
openUniqueness between two or more CRUSH ruleset choose statements
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
Assuming that ceph-node1 is in default root, when we define and assign following crush rule:
rule primary_as_host_2 { ruleset 2 type replicated min_size 1 max_size 10 step take ceph-node1 step choose firstn 1 type osd step emit step take default step chooseleaf firstn -1 type host step emit }
pool can get duplicated osd in the acting set (osd on ceph-node1 is returned by both of the choose statement ) . I'll be nice to have an option to force uniqueness globally.
No data to display
Actions