On Mon, Jun 23, 2014 at 4:11 AM, Guang Yang <yguang11@xxxxxxxxxxx> wrote: > Hello Yehuda, > I drafted a brief summary for the status of the bucket index sharding blueprint and put it here - http://pad.ceph.com/p/GH-bucket-index-scalability, it would be nice you can take a look to see if there is anything I missed, I also posted the pull request here - https://github.com/ceph/ceph/pull/2013. Just one note regarding the blueprint, other BI log operations will need to use the new schema too (e.g., log trim operations). I was thinking a bit about how to do resizing and dynamic sharding later on. My thought was that we'd have two bucket prefixes: one for read and delete operations, and one for read, write and delete operations. Normally both will point at the same prefix and we'll just access a single one. But when we're resizing we'll need to use both. If we're listing objects we'll access both sets of shards and merge everything). If we're creating object we'll just create it in the second one. Removing object, we'll remove it from both. The above description is a bit vague, and shouldn't really change what we do now. Just that the implementation needs to maybe abstract that bucket access decision nicely so that in the future we could implement this easily. Sadly I'll be off for this CDS, but I'm sure Josh, Greg, Sage, and others will be able to help there. Thanks, Yehuda -- 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
