Steps to create a unallocated db for a distributed db [speaking lmdb specifically]
I am dealing with lmdb and lmdb very quickly. But one problem with it - lmdb is not distributed. Every time I need some maintenance the lmdb has to be taken down and the sites are unavailable for hours. I am investigating how to make lmdb distributed by implementing replication capabilities. So far the closest I've been to this dynomite netflix codebase.
The problem is that it is currently applicable for redis and memcache, but it says generic, so it can be used for lmdb as well. I am handling lmdb with python using py-lmdb bindings
I don't know how to approach it from an lmdb perspective in the python world, since the code must also be written in python bindings.
Any help would be greatly appreciated.
source to share
LMDB is for embedded DB engine only. Propagation / replication is at a higher level. For example, you can use HyperDex with an LMDB backend. https://github.com/hyc/HyperDex/tree/lmdb . There's also memcachedb built on LMDB and ardb or ledisdb for redis compatible servers running on top of LMDB.
https://gitorious.org/mdb/memcachedb/source/9f2e5415e4d9017889caf61c100a9b8652825319 :
So, you can use them with dynomite if you like.
source to share
You can remove LMDB (built in ARDB) to replace Redis in Dynomite to make LMDB a distributed system. We did a POC on this and they worked.
For more information, you can check out our open issues at https://github.com/Netflix/dynomite/issues/254
source to share