Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement key count estimation via AAE trees #1030

Merged
merged 2 commits into from Dec 19, 2014
Merged

Implement key count estimation via AAE trees #1030

merged 2 commits into from Dec 19, 2014

Commits on Oct 7, 2014

  1. Update K/V hashtrees to support key estimation 

    This commit updates riak_kv_index_hashtree to provide an API around
the new AAE-based key count estimation feature added to the hashtree
module in riak_core.

This provides a mechanism to estimate the number of keys in a given K/V
vnode based on its AAE trees.

This estimate is used to enable an improvement in the operation of
AAE-based fullsync replication in Riak Enterprise.

Authored-by: Mikael Lixenstrand <mikael.lixenstrand@erlang-solutions.com>
Rebased-by:  Joseph Blomstedt <joe@basho.com>
    @jtuple
    Mikael Lixenstrand authored and jtuple committed Oct 7, 2014
    Configuration menu
    Copy the full SHA
    fd443c2 View commit details
    Browse the repository at this point in the history

  2. Make AAE key estimation API handle illegal IndexN 

    This commit changes riak_kv_index_hashtree to return not_responsible
when provided an illegal IndexN in estimate_keys/2. Prior to this
commit, an invalid IndexN would cause the hashtree process to crash.

Authored-by: Kresten Krab Thorup <krab@trifork.com>
Rebased-by:  Joseph Blomstedt <joe@basho.com>
    @krestenkrab @jtuple
    krestenkrab authored and jtuple committed Oct 7, 2014
    5 Configuration menu
    Copy the full SHA
    5b47019 View commit details
    Browse the repository at this point in the history