Ok, thats the way it should be.. :) But specializing a little more the question.. whats the data partition scheme between nodes, how can a user control it.. block level? file level? suppose that i have agregations that i want it to stick together in nodes... even if replicated in several nodes.. but always together, to get network roundtrips diminished.. thanks again On Wed, Apr 27, 2011 at 4:24 PM, Gregory Farnum <gregory.farnum@xxxxxxxxxxxxx> wrote: > We're not quite sure what construct you're referring to here with "block pointer"? > > Generally users of the Ceph client do not need to know about the position or movement of data on the storage cluster, though, if that answers your question. :) > -Greg > On Wednesday, April 27, 2011 at 12:18 PM, Fabio Kaminski wrote: >> Suppose that i have a datastructure with a block pointer to another >> item(block).. >> how this pointer would work with ceph, if this block get moved to >> another data node, would it still work? >> >> what is the best way to do it under ceph? im using cephs own userland libs.. >> >> block pointers? its safe? how.. :) >> >> thanks, >> >> Fabio Kaminski >> -- >> 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
