4 ms·
> It is possible to mount an EBS volume and have RethinkDB store your data on it, but that setup is not available out of the box. That's a curious default choi
by crazygringo 13y ago
> It is possible to mount an EBS volume and have RethinkDB store your data on it, but that setup is not available out of the box.
That's a curious default choice. It's hard for me to imagine why you'd ever want to run RethinkDB on local instance storange, instead of EBS, given that EBS is much more reliable, is easier to back up, can be swapped between instances, etc. (Or is this AMI more for just trying out, not for actual production use?)
Obviously, EBS has its problems, but so does local instance storage.
Also: I remember that way-back-when, RethinkDB was touted as being designed for SSD's from the ground up. Is that still the case? Would running on provisioned-IOPS EBS provide a huge benefit over regular EBS or regular local storage?
- jdoliner 13y agoI know the answer to your last question which is that the SSD optimized code is all present as the serializing layer so running on SSDs will provide a significant performance boost. I'm not 100% sure what provisioned-IOPS EBS is but I'm guessing from context that it's solid state based?
- mryan 13y agoNo, it's just plain ol' EBS which delivers a minimum of X IOPS, where X is between 100 and 2000 (unless they have improved this since I last checked). AWS does have some SSD-based storage, but only for the larger instance types.
- deleted 13y ago[deleted]
- atnnn 13y agoThe documentation is misleading. RethinkDB instances launched from the Marketplace all run on an EBS volume.
- coffeemug 13y agoFor anyone reading this, the docs have been fixed. Sorry -- it was my screwup.
- rzimmerman 13y agoIt looks like for now you need to manually edit a config file to get this working with additional EBS volumes, but the wording implies better support is coming.
- deleted 13y ago[deleted]