Afternoon, Evening, Morning to All -
Big Recap for today: lots of Q & A, new code, meetups, and more.
Happy New Year.
Mark
Community Manager
Basho Technologies
wiki.basho.com
twitter.com/pharkmillups
---
Riak Recap for December 28 - January 3
===
Hi,
we are trying use Riak as a storage layer for experimental
higher-level data types updated by clients, using a set of
well-defined operations. To this end, each data type instance is
stored under a single key. One problem with this approach is that
after client modifies even a small piece of t
Oh I see! Thanks for the correction.
--
Pronam Chatterjee
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Wednesday 4 January 2012 at 7:35 PM, Sean Cribbs wrote:
> Pronam,
>
> That is a different setting entirely and not related to normal delete
> operations.
>
> On Wed, Jan 4, 2
Pronam,
That is a different setting entirely and not related to normal delete
operations.
On Wed, Jan 4, 2012 at 8:57 AM, Pronam Chatterjee wrote:
> If you are using bit cask, it takes a while before the space will be
> freed. I think the default is 24 hours. Below is a quote from the bit cask
If you are using bit cask, it takes a while before the space will be freed. I
think the default is 24 hours. Below is a quote from the bit cask page on the
wiki.
Purging stale entries after a fixed period
To automatically purge stale values, set the expiry_secs value to the desired
cutoff t
Vicky,
Riak is very careful about deletes and will not completely reap existing
values until several conditions occur. So instead of deleting the value
immediately -- because in a distributed system, race-conditions can occur
and you need to determine causal ordering of events -- Riak will write a
Hi,
I had around 100 million entries in the riak cluster of 4 which was taking 9*4
= 36 GB of RAM.
I deleted some 40 million keys from the cluster and still the size is same.
I restarted the cluster and still size is same.
Can anyone please tell why riak is still retaining its original size even
