You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no mention in the docs of Riak Repl fullsync_strategy. This can be set in advanced.config under the riak_repl section. When not set, it uses the default setting is keylisting but the other option is to set {fullsync_strategy, aae} which will then use legacy AAE hashtrees to sync data between the two clusters. It is slightly more efficient than keylisting but has a number of issues that such as not being able to sync partitions if the sink cluster happens to be rebuilding that hashtree at the time of the attempt.
The spam in the logs generated by this latter one can be reduced by telling Riak to soft fail on items such as this by also adding {max_fssource_soft_retries, 3}, to the riak_repl section of advanced.config
The text was updated successfully, but these errors were encountered:
There is no mention in the docs of Riak Repl fullsync_strategy. This can be set in advanced.config under the riak_repl section. When not set, it uses the default setting is keylisting but the other option is to set
{fullsync_strategy, aae}
which will then use legacy AAE hashtrees to sync data between the two clusters. It is slightly more efficient than keylisting but has a number of issues that such as not being able to sync partitions if the sink cluster happens to be rebuilding that hashtree at the time of the attempt.The spam in the logs generated by this latter one can be reduced by telling Riak to soft fail on items such as this by also adding
{max_fssource_soft_retries, 3},
to the riak_repl section of advanced.configThe text was updated successfully, but these errors were encountered: