Key removal using Bitcask and expiry_secs

Hi there, When expired, at what point will the key be removed from memory? Is the expiration process automated, or trigged by a read? Scott ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.b

Re: Bitcask and expiry_secs

it physically exists. Data removal happens during the merge > process. > > Pavan > > From: Scott Hyndman > Date: Monday, November 12, 2012 1:33 PM > To: > Subject: Bitcask and expiry_secs > > Hi there, > > When expired, at what point will the key be removed f

Ruby Riak client -- threadsafe?

Hi there, I noticed this post from a bit over a year ago ( http://lists.basho.com/pipermail/riak-users_lists.basho.com/2011-June/004592.html), and wondered whether this was still the case. I've noticed one detail suggesting that it may be (the fact that Ripple creates a client per thread), and one

Bitcask and expiry_secs

Hi there, When expired, at what point will the key be removed from memory? Is the expiration process automated, or trigged by a read? Thanks! Scott ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users

Re: Ruby Riak client -- threadsafe?

gt; instantiating it in the Railtie instead to be used by all threads. > > On Mon, Nov 12, 2012 at 5:01 PM, Scott Hyndman > wrote: > > Hi there, > > > > I noticed this post from a bit over a year ago > > ( > http://lists.basho.com/pipermail/riak-users_lists.basho.com