riak-3.1-multi_bitcask_instances

riak-3.1-multi_bitcask_instances

2.2.13

Config change to point to riak_core 2.2.13 worker_pool bug fix changes.

riak-2.2.8-workerpool-shutdown-bugfix

riak-2.2.8-workerpool-shutdown-bugfix

riak-2.2.8-multi_bitcask_instances

riak-2.2.8-multi_bitcask_instances

Riak-2.2.12 AAE Deletion Fix

KeyHashes were not deleted from the hashtree when they expired. Causing a lot of issues and possible race conditions on exchanges.

The following have been done to remedy this:

Deleted:

Adding expiry to the objects hash.
Hashtree has been reverted to its form from develop 2.2. before the itr_filter_fun.

Added:

Filter functionality with will ignore keys that have an expiry time (in bitcask fold)
On update_hashtree if the key has an exipry_time (in riak_kv_vnode) it will delete it from the hashtree (via riak_kv_index_hashtree) as it was not kept in bitcask (see previous).
Functions in riak_kv_bitcask_backend and bitcask.erl have been updated to accept options from riak, so It will check whether or not it should ignore keys on the fold.

Bugfix: False Positive Fullsync Differences

This bugfix will compare fullsync object hash versions between paired fullsync partners.
It will use the highest fullsync object hash version (highest = 1)
Version 1 changes the method of hashing the entire object, to hashing a sorted vclock.

This removes false positive differences generated from riak tombstones that have differently ordered metadata dictionaries, due to the additional metadata "X-Riak-Tstamp-Expire".

This should significantly reduce the time taken to complete a fullsync when a large number of deletes are present.

Vnode Crash On Shutdown Fix

This release is a fix that prevents the hastree's from being updated on a shutdown.
For hashtree's with a large amount of data in, this was taking longer than 60 seconds causing the node to crash on the way down. Compared to stopping in a graceful manner

Partial Merge Fix

This release is bringing in two bug fixes:

1. Fix for partial merge which bring's back old stale deleted (expired) data in bitcask on reboot
2. Stop loading expired keys into memory on startup

riak-2.2.8-split_backend

riak-2.2.8-split_backend