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.basho.com
Re: Bitcask and expiry_secs
Fantastic. Thank you. On 12 November 2012 19:01, Pavan Venkatesh wrote: > Hi Scott, > > Key is removed immediately from the in-memory hash table "keydir", when > expired. One cannot access the value of that key after expiry, meaning "the > data", although 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 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_lists.basho.com > ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
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 that contradicts (the existence of HTTP and PB connection pools on the client). Can anyone shed some insight? Scott ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
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_lists.basho.com
Re: Ruby Riak client -- threadsafe?
Great. Thanks Sean. On 13 November 2012 10:37, Sean Cribbs wrote: > Scott, > > It is generally safe to use the Ruby client from multiple threads. A > few items that are infrequently touched (memoized buckets and their > properties) are not, but normal requests are all handled by a > thread-safe connection pool. Ripple historically kept a client in the > thread-locals in order to have a sort of globally-referrable Client > instance; similar to how ActiveRecord's connections work, but not as > sophisticated. This could be improved in the future, perhaps > 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/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 that contradicts (the existence of HTTP and PB > connection > > pools on the client). > > > > Can anyone shed some insight? > > > > Scott > > > > ___ > > riak-users mailing list > > riak-users@lists.basho.com > > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > > > > > -- > Sean Cribbs > Software Engineer > Basho Technologies, Inc. > http://basho.com/ > ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
