Surveying different storage engines used with Voldemort

[Vinoth Chandar]

So, its well known I guess, that at Linkedin we use BDB-JE in production as the backend for Voldemort.  I was just curious to see what others are doing and probably share some experiences.

Please list your storage engine if different from BDB je

Thanks
Vinoth

[Francois]

We use now our own storage, called DiskMap. There will be soon a
couple of articles on our blog explaining how we use Voldemort
(modified hashing) and why we introduced this new storage.

But quickly, everything came from the problems running BdB on
commodity hardware (so motherboards with limited RAM) and plenty of
disk space. If the Bdb RAM formula is not matched, this is terribly
slow.

We also wanted to have a partition aware storage, with rebuilds
working on a disk matching basis (so no RAID required, and local copy
possible via a spare slot).

But this is a very specific way of using it, it would have some
drawbacks for other usages ( optimized for last access date caching,
no local range queries so eventually consistent BTrees on top of the
ring are a must, per store configuration requiring to guess the data
volume distribution between stores ).

François

On Jun 27, 2:49 am, Vinoth Chandar <mail.vinoth.chan...@gmail.com>
wrote:

[Vinoth Chandar]

sounds very interesting. Please update the community once the blog is out.

[Francois]

http://www.yobidrive.com/blog

Article about DiskMap is still to be written, as well as one about the
Voldemort choice (vs Cassandra or other KV rings) . Takes time,
because we try to write it in a not too too technical way!




On Jul 3, 9:05 am, Vinoth Chandar <mail.vinoth.chan...@gmail.com>
wrote: