On Wed, Oct 10, 2012 at 9:23 AM, Sage Weil <sage@xxxxxxxxxxx> wrote: > I certainly wouldn't recommend it, but there are probably use cases where > it makes sense (i.e., the data isn't as important as the performance). This would make a lot of sense for e.g. service orchestration-style setups where you run an elastic pool of webapps. The persistent storage is the database, not the local disk, but you might still e.g. spool uploads to local disk first, or have a local cache a la varnish. Crashing a machine in such a setup tends to mean deleting the image, not trying to recover it. Also, for anyone running virtualized mapreduce worker nodes.. Cephfs plugged in as the FS, compute wanting local storage for the temporary files, but crashes just mean the task is restarted elsewhere.. (Now, in both of the above, you might ask, why not use a local disk for this then, why use RBD? Because a lot of people are interested in running diskless compute servers, or ones booting off of a minimal SSD/SD-card, with just the base OS, no vm images stored locally. Tremendously helps with density, especially on low-power platforms like ARM.) -- 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
