Multi-backend and retiring storage

Matt Black matt.black at jbadigital.com
Tue Aug 26 20:53:43 EDT 2014


Hello list,

Apologies in advance for the longish preamble - the question (when I get to
it) is fairly straight forward.

We’ve been happily running Riak for a couple of years now using
multi-backend to map various buckets onto different disk locations (for
infosec compliance reasons).

Our config is essentially this:

{riak_kv, [
        {storage_backend, riak_kv_multi_backend},

        %% Configure multiple eleveldb storage locations
        {multi_backend_default, <<"default">>},
        {multi_backend, [
            %% Default fallback: this is unused
            {<<"default">>, riak_kv_eleveldb_backend, [
                {data_root, "/mnt/riak/eleveldb/default"}
            ]},
            %% Storage1
            {<<"eleveldb_storage1">>, riak_kv_eleveldb_backend, [
                {data_root, "/mnt/riak/eleveldb/storage1"}
            ]},
            %% Storage2
            {<<"eleveldb_storage2">>, riak_kv_eleveldb_backend, [
                {data_root, "/mnt/riak/eleveldb/storage2"}
            ]},
            ...

Bucket properties then map Riak buckets onto the relevant backend.

Again for infosec compliance reasons, we need to “retire” one of our
backends, and the data contained therein.

What would a process be for doing this? What happens across the cluster as
I remove the config from each node? At what point can I safely delete the
data directories?

Thanks
Matt
​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20140827/335e090b/attachment.html>


More information about the riak-users mailing list