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

Steve Vinoski e6dc7a5936 fix new config problems, tests all pass again The tests pass but there's still a "NIF upgrade" error reported at the end of each test run. Will fix later.		2013-03-11 11:12:12 -04:00
c_src	Renaming from wterl to wt (less redundant and more meaningful name)	2013-03-10 21:42:31 -04:00
src	fix new config problems, tests all pass again	2013-03-11 11:12:12 -04:00
.gitignore	fix new config problems, tests all pass again	2013-03-11 11:12:12 -04:00
enable-wt	Renaming from wterl to wt (less redundant and more meaningful name)	2013-03-10 21:42:31 -04:00
Makefile	Renaming from wterl to wt (less redundant and more meaningful name)	2013-03-10 21:42:31 -04:00
README.md	Renaming from wterl to wt (less redundant and more meaningful name)	2013-03-10 21:42:31 -04:00
rebar	update rebar and rebar.config	2012-10-26 09:25:35 -04:00
rebar.config	Renaming from wterl to wt (less redundant and more meaningful name)	2013-03-10 21:42:31 -04:00

README.md

wt 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 wt:session_create function currently returns an error under certain circumstances, so we currently ignore its return value.
The riak_kv_wt_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_wt_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 wt into a Riak devrel cluster using the enable-wt script. Clone the riak repo, change your working directory to it, and then execute the enable-wt script. It adds wt as a dependency, runs make all devrel, and then modifies the configuration settings of the resulting dev nodes to use the WiredTiger storage backend.