umgeher/leveled
0
Fork 0
Code Issues Pull requests Releases Activity Actions

Updated docs

Browse source
This commit is contained in:
martinsumner 2017-02-28 00:15:06 +00:00
parent 21c8b94437
commit 5235aa1adb
2 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -100,4 +100,4 @@ This will start a new Bookie. It will start and look for existing data files, u
The book_start method should respond once startup is complete. The leveled_bookie module includes the full API for external use of the store. The book_start method should respond once startup is complete. The leveled_bookie module includes the full API for external use of the store.
Read through the [end_to_end test suites](test/end_to_end/) for further guidance. Running in Riak requires one of the branches of riak_kv referenced [here](docs/FUTURE.md). There is a [Riak branch](https://github.com/martinsumner/riak/tree/mas-leveleddb) intended to support the automatic build of this, and the configuration via cuttlefish. However, the auto-build fails due to other dependencies bringing in an alternative version of riak_kv, and the configuration via cuttlefish is broken for reasons unknown. Building this from source as part of Riak will require a bit of fiddling around.

4
docs/FUTURE.md
View file

@ -114,4 +114,6 @@ The other n-1 vnodes must also do a local GET before the vnode PUT (so as not to
This branch changes the behaviour slightly at the non-coordinating vnodes. These vnodes will now try a HEAD request before the local PUT (not a GET request), and if the HEAD request contains a vclock which is <strong>dominated</strong> by the updated PUT, it will not attempt to fetch the whole object for the syntactic merge. This branch changes the behaviour slightly at the non-coordinating vnodes. These vnodes will now try a HEAD request before the local PUT (not a GET request), and if the HEAD request contains a vclock which is <strong>dominated</strong> by the updated PUT, it will not attempt to fetch the whole object for the syntactic merge.
This should save two object fetches (where n=3) in most circumstances. This should save two object fetches (where n=3) in most circumstances.
Note, although the branch name refers to the put fsm - the actual fsm is unchanged by this, all of the changes are within vnode_put