On Fri, Aug 31, 2012 at 11:59 AM, Atchley, Scott <[email protected]> wrote: > I think what he is looking for is not to bring data to a client to convert > from replication to/from erasure coding, but to have the servers do it based > on some metric _or_ have the client indicate which file needs to be converted > and have the servers do the work. > > I believe what you are saying is that I can have a directory using the > replicated pool and another directory (or sub-directory) that uses the coding > pool. The client would then copy the file from one directory to the other. > The question becomes "Who does the erasure encoding?". The client (read back > from the replica pool and write to the erasure pool) or the servers (copy > data to the erasure pool and calculate on the servers)?
I was aiming more for "I can see where this could sit in the architecture". You don't have to make the client effectively download and re-upload a file; that logic can be pushed closer to the OSDs. -- 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
