Thanks!

On Mon, Nov 9, 2015 at 2:23 PM, Luke Bakken <lbak...@basho.com> wrote:

> Hi Ricardo,
>
> You want to put it it the top-level of your app.config file, in the
> bitcask section:
>
>  {bitcask,
>      [{io_mode,erlang},
>       {merge_window,...},
>       ...,
>       ...
>       ]},
>
>
> http://docs.basho.com/riak/1.4.9/ops/advanced/backends/multi/
>
> --
> Luke Bakken
> Engineer
> lbak...@basho.com
>
> On Mon, Nov 9, 2015 at 6:31 AM, Ricardo Mayerhofer <ricardo....@gmail.com>
> wrote:
>
>> Hi,
>> Riak 1.4 documentation states:
>> "Certain settings, such as Bitcask's merge_window, are set per-node,
>> rather than per-backend, and as such must be set in the top level backend
>> sections of your app.config."
>>
>> However I'm unsure where to put it in app.config file when using
>> multi-backend, given there is no example. Should it be inside riak_kv
>> section? Any help is appreciated. Thanks.
>>
>>  {riak_kv, [
>>
>>             %% Storage_backend specifies the Erlang module defining the
>> storage
>>
>>             %% mechanism that will be used on this node.
>>
>>             {storage_backend, riak_kv_multi_backend},
>>
>>             {multi_backend_default, <<"be_default">>},
>>
>>             {multi_backend, [
>>
>>               {<<"be_leveldb">>, riak_kv_eleveldb_backend, [
>>
>>                   {data_root, "/mnt/riak-data/leveldb"}
>>
>>               ]},
>>
>>                 {<<"be_default">>, riak_kv_bitcask_backend, [
>>
>>                   {data_root, "/mnt/riak-data/bitcask"}
>>
>>               ]}
>>
>>             ]},
>>
>> *           %% Here?*
>>
>> *            {merge_window, {1,3}},*
>>
>> --
>> Ricardo Mayerhofer
>>
>> _______________________________________________
>> riak-users mailing list
>> riak-users@lists.basho.com
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>>
>


-- 
Ricardo Mayerhofer
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to