Unfortunately this part doesn't fit into the CRUSH language. In order
to do it and segregate properly by node you need to have separate SSD
and HDD nodes, rather than interspersing them. (Or if you were brave
you could set up some much more specified rules and pull each replica
from a different rack/row, but that would take a bit of work and
enough machines for that mechanism to be useful.)
-Greg
On Tue, Feb 12, 2013 at 12:40 PM, ymorita000@xxxxxxxxx
<ymorita000@xxxxxxxxx> wrote:
> Hi,
>
> I am trying to test a storage tiering using the following
> "ssd-primary" rule set introduced in the Ceph page. However, there
> seems to be a chance that primary pg and replica pg are placed on the
> same node.
>
> Is there any way to avoid this at this point in time?
>
> rule ssd-primary {
> ruleset 4
> type replicated
> min_size 0
> max_size 10
> step take ssd
> step chooseleaf 1 type host
> step emit
> step take platter
> step chooseleaf -1 type host
> step emit
> }
>
> Ceph - CRUSH Maps
> http://ceph.com/docs/master/rados/operations/crush-map/#placing-different-pools-on-different-osds
>
> Thank you.
> Yuji
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
