On 22/05/13 06:18, Idan Shinberg wrote:
Thus , I fear Riak never treats their data as "dead-bytes" and they
never get merged

I created 2 buckets using s3cmd and made several tens of uploads  of
32mb sized files , deleting them right afterwards ( with proper s3cmd
commands , of course) .

I ended up with no buckets and no keys in my riak s3 database ,
however , directory /var/lib/riak/bitcask/ 64 partitions now occupy 15GB
worth of space

several riak restarts did not trigger any merges , and my merge settings
are set to impose very though merge triggering criterias , So I'm
guessing the only reason the data is not being cleared is the fact that
it's still in use ...

Relevant riak-cs config :


Have you tried adjusting the leeway_seconds and gc_intervals?
I think Riak CS hangs onto things for a day by default.. Your config below looked like you'd tried changing that to 30 seconds, but I wonder if maybe that's actually *too fast*? Maybe try something like 15 minutes?

I don't know though.. just a thought I'd had.


/*              %% == Garbage Collection ==*/
/*
*/
/*              %% The number of seconds to retain the block*/
/*              %% for an object after it has been deleted.*/
/*              %% This leeway time is set to give the delete*/
/*              %% indication time to propogate to all replicas.*/
/*              %% 86400 is 24-hours.*/
/*              {leeway_seconds, 30},*/
/*
*/
/*              %% How often the garbage collection daemon*/
/*              %% waits in-between gc batches.*/
/*              %% 900 is 15-minutes.*/
/*              {gc_interval, 60},*/
/*
*/
/*              %% How long a move to the garbage*/
/*              %% collection to do list can remain*/
/*              %% failed, before we retry it.*/
/*              %% 21600 is 6-hours.*/
/*              {gc_retry_interval,300},*/




_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to