On Thu, Jun 16, 2011 at 09:19:51AM -0700, Greg Nelson wrote: > "A tombstone > is put and then an async get is fired off and if the async get finds all > the primary nodes in the preflist are up, it does the delete. If not, > the next time the key is fetched, it does the same check again and will > do the delete then if the downed node is up." > > What if the key is never fetched again after the node is up? Does this mean > one would have to do GETs on all keys deleted while the node was down after > the node is back online, in order to reclaim that space?
As I said, we know this is not the ideal solution. We have a proposal internally that should solve this issue by not relying on GETs to trigger actually erasing the key. If this really concerns you, you could implement something like postgres's VACUUM by doing a keylist and doing a fetch on all keys in a slow background process (while you know all the nodes are up) to force the issue. Andrew _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
