On Apr 18, 2013, at 2:08 PM, Josh Durgin <[email protected]> wrote:
> I talked to some folks interested in doing a more limited form of this > yesterday. They started a blueprint [1]. One of their ideas was to have > erasure coding done by a separate process (or thread perhaps). It would > use erasure coding on an object and then use librados to store the > rasure-encoded pieces in a separate pool, and finally leave a marker in > place of the original object in the first pool. This sounds at a high-level similar to work out of Microsoft: https://www.usenix.org/system/files/conference/atc12/atc12-final181_0.pdf The basic idea is to replicate first, then erasure code in the background. - Noah -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
