-
Here's counterexample Cp8:
```
Cp8 = [[{set,{var,1},{call,bitcask_pulse,bc_open,[true,{true,{62,59,175},26}]}},{set,{var,2},{call,bitcask_pulse,puts,[{var,1},{2,3},]}},{set,{var,6},{call,bitcask_puls…
-
Use [papers-we-love](https://github.com/papers-we-love/papers-we-love) to find and read papers
-
The bitcask.merge_check_jitter was added to avoid the regular bitcask merge check done every 3 mins from triggering synchronized merges on many vnodes at once. It was observed at a large customer rece…
-
Our recommendation against using Active Anti-Entropy with Bitcask Expiry needs to be documented, likely here: http://docs.basho.com/riak/latest/theory/concepts/aae/
The usage of Active Anti-Entropy w…
-
Bitcask is now supporting `async_fold` all the time now, so some simple refactoring work can remove all of the async_fold=false cases in riak_kv_bitcask_backend.erl.
-
According to the docs at [http://docs.basho.com/riak/latest/ops/advanced/configs/configuration-files/#Bitcask] , the default value of `bitcask.expiry.grace_time` is 0. If you set this value in riak.c…
-
We should duplicate the behavior of erlang's bitcask
-
The current merge strategy leaves some things to be desired. We should try to imitate bitcask more closely, here.
-
There appears to be a potential process leak when a bitcask_file process is unable to open a file. When this occurs, the process will return an error to the caller of file_open, but will not shut itse…
-
https://github.com/roseduan/rosedb
https://riak.com/assets/bitcask-intro.pdf