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

Allow nextgenrepl to real-time replicate reaps (#6) #1879

Open
wants to merge 1 commit into
base: develop-3.0
Choose a base branch
from
Open

Allow nextgenrepl to real-time replicate reaps (#6) #1879

wants to merge 1 commit into from

Commits on Nov 14, 2023

  1. Allow nextgenrepl to real-time replicate reaps (#6) 

    * Allow nextgenrepl to real-time replicate reaps

This is to address the issue of reaping across sync'd clusters.  Without this feature it is necessary to disable full-sync whilst independently replicating on each cluster.

Now if reaping via riak_kv_reaper the reap will be replicated assuming the `riak_kv.repl_reap` flag has been enabled.  At the receiving cluster the reap will not be replicated any further.

There are some API changes to support this.  The `find_tombs` aae_fold will now return Keys/Clocks and not Keys/DeleteHash.  The ReapReference for riak_kv_repaer will now expect a clock (version vector) not a DeleteHash, and will also now expect an additional boolean to indicate if this repl is a replication candidate (it will be false for all pushed reaps).

The object encoding for nextgenrepl now has a flag to indicate a reap, with a special encoding for reap references.

* Update riak_object.erl

Clarify specs

* Take timestamp at correct point (after push)

* Updates following review

* Update rebar.config
    @martinsumner
    martinsumner committed Nov 14, 2023
    Configuration menu
    Copy the full SHA
    9f4a557 View commit details
    Browse the repository at this point in the history