Disabling CRUSH for erasure code and doing custom placement

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

CRUSH placement algorithm works really nice with replication. However,
with erasure code, my cluster has some issues which require making
changes that I cannot specify with CRUSH maps.
Sometimes, depending on the type of data, I would like to place them
on different OSDs but in the same pool.

I realize that to disable the CRUSH placement algorithm and replacing
it with my own custom algorithm, such as random placement algo or any
other, I have to make changes in the source code. I want to ask if
there is an easy way to do this without going into every code file and
looking where the mapping from objects to PG is done and changing
that. Is there some configuration option which disables crush and
points to my own placement algo file for doing custom placement.

Let me know about the most neat way to go about it. Appreciate any
help I can get.

Regards,
Shayan Saeed
Research Assistant, Systems Research Lab
University of Illinois Urbana-Champaign
--
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




[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux