Configuring Riak CS Multi-Datacenter
Please note that Riak CS Enterprise requires a download separate from the open-source Riak CS, which will not work in conjunction with Riak Enterprise.
Configuring Multi-Datacenter Replication in Riak CS requires the
addition of a new group of settings to the app.config
configuration
file for all Riak CS and Riak Enterprise nodes that are part of the Riak
CS cluster.
Riak Enterprise Configuration
As of Riak release 1.4.0, there are two different MDC replication modes that Riak CS can use to request data from remote clusters. Please see the comparison doc for more information.
Replication Version 3 Configuration
For each Riak node in the cluster, update the mdc.proxy_get
setting in
riak.conf
, or by appending the {proxy_get, enabled}
setting to the
riak_repl
section of the old-style advanced.config
or app.config
files,
as shown in the following example:
mdc.proxy_get = on
{riak_repl, [
%% Other configs
{fullsync_on_connect, true},
{fullsync_interval, 360},
{data_root, "/var/lib/riak/data/riak_repl"},
{proxy_get, enabled}
%% Other configs
]}
{riak_repl, [
%% Other configs
{fullsync_on_connect, true},
{fullsync_interval, 360},
{data_root, "/var/lib/riak/data/riak_repl"},
{proxy_get, enabled}
%% Other configs
]}
Version 3 replication requires additional configuration in the source cluster via the command line.
riak-repl proxy_get enable <sink_cluster_name>
The sink_cluster_name
should be replaced with the name of your
configured sink cluster.
See also:
Riak CS Configuration
For each Riak CS node in the cluster, update the riak_cs
section of the
advanced.config
, or the old-style app.config
files, by appending the
proxy_get
setting as shown in the following example:
{riak_cs, [
%% Other configs
{proxy_get, enabled},
%% Other configs
]}
{riak_cs, [
%% Other configs
{proxy_get, enabled},
%% Other configs
]}
Stanchion Configuration
Though there is no specific configuration for Stanchion, note that Stanchion should be a single, globally unique process to which every Riak CS node sends requests, even if there are multiple replicated sites. Unlike Riak and Riak CS, Stanchion should run on only one node in a given cluster, perhaps on its own, dedicated hardware if you wish. Stanchion runs on only one node because it manages strongly consistent updates to globally unique entities like users and buckets.