Can Bitcask expiry_secs vary between backends?

Tom Santero tsantero at basho.com
Thu Apr 4 22:42:11 EDT 2013


Hey Toby,

Your conclusions are correct.

Tom

On Thu, Apr 4, 2013 at 10:39 PM, Toby Corkindale <
toby.corkindale at strategicdata.com.au> wrote:

> On 04/04/13 17:43, Toby Corkindale wrote:
>
>> Hi,
>> Can we set Bitcask's expiry_secs value to be different per backend, in a
>> Multi-backend scenario?
>>
>> Eg.
>>
>> {multi_backend, [
>>      {<<"bitcask_short_ttl">>,  riak_kv_bitcask_backend, [
>>          {expiry_secs, 3600},       %% Expire items after one hour
>>          {expiry_grace_time, 600}
>>      ]},
>>      {<<"bitcask_long_ttl">>,  riak_kv_bitcask_backend, [
>>          {expiry_secs, 86400},       %% Expire items after one day
>>          {expiry_grace_time, 3600}
>>      ]},
>>      {<<"eleveldb_mult">>, riak_kv_eleveldb_backend, [
>>      ]}
>> ]},
>>
>>
>> And if we're re-using bitcask in this way, do we need to specify
>> anything else, such as different data directories per backend?
>>
>
>
> Answering my own question here, but..
> Experimentation seems to indicate that
> a) You can set different expiry periods per bitcask backend.
> b) You must set a unique data_dir for each backend, or else
> everything crashes after a while.
>
> -Toby
>
>
>
> ______________________________**_________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/**mailman/listinfo/riak-users_**lists.basho.com<http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20130404/eae94278/attachment.html>


More information about the riak-users mailing list