greg/wterl: This is a Riak storage backend that uses WiredTiger, an Erlang interface to the WiredTiger k/v pair storage engine, and an abstract async thread-pool layer for Erlang's NIF API called `c_src/async_nif.h`.

greg/wterl

This is a Riak storage backend that uses WiredTiger, an Erlang interface to the WiredTiger k/v pair storage engine, and an abstract async thread-pool layer for Erlang's NIF API called c_src/async_nif.h.

Find a file

Gregory Burd 264d189947 Update defaults		2012-12-04 14:29:07 -05:00
c_src	Ensure we have the proper number of arguments first. Pass configuration information on session open. Fix a few mistakes for preconditions.	2012-12-04 14:26:46 -05:00
src	Update defaults	2012-12-04 14:29:07 -05:00
.gitignore	add emacs backup files to .gitignore	2012-02-16 13:32:29 -05:00
enable-wterl	modify enable-wterl to avoid adding wterl repeatedly	2012-10-26 10:22:59 -04:00
Makefile	Another useful debugging target.	2012-11-29 21:16:23 -05:00
README.md	add README	2012-03-27 22:27:50 -04:00
rebar	update rebar and rebar.config	2012-10-26 09:25:35 -04:00
rebar.config	add editor settings to rebar.config	2012-10-26 10:25:02 -04:00

README.md

wterl is an Erlang interface to the WiredTiger database, and is written to support a Riak storage backend that uses WiredTiger.

This backend currently supports only key-value storage and retrieval.

Remaining work includes:

The wterl:session_create function currently returns an error under certain circumstances, so we currently ignore its return value.
The riak_kv_wterl_backend module is currently designed to rely on the fact that it runs in just a single Erlang scheduler thread, which is necessary because WiredTiger doesn't allow a session to be used concurrently by different threads. If the KV node design ever changes to involve concurrency across scheduler threads, this current design will no longer work correctly.
Currently the riak_kv_wterl_backend module is stored in this repository, but it really belongs in the riak_kv repository.
There are currently some stability issues with WiredTiger that can sometimes cause errors when restarting KV nodes with non-empty WiredTiger storage.

Future support for secondary indexes requires WiredTiger features that are under development but are not yet available.

Deploying

You can deploy wterl into a Riak devrel cluster using the enable-wterl script. Clone the riak repo, change your working directory to it, and then execute the enable-wterl script. It adds wterl as a dependency, runs make all devrel, and then modifies the configuration settings of the resulting dev nodes to use the WiredTiger storage backend.