Antonio,
Here is a detailed discussion of the Riak / leveldb delete scenario:
https://github.com/basho/leveldb/wiki/mv-aggressive-delete
Pay close attention to the section titled “Update April 6, 2014”. This
explains why as much as 4.2G bytes per vnode might remain within leveldb after
deleting all keys. There is no mechanism to override the logic that causes the
disk space retention.
One workaround is to use Riak’s handoff mechanism to transfer vnodes from one
physical server to another. The vnode transfer will remove all deletion
tombstones on the destination. The last step of the transfer then deletes all
leveldb files on the original server, recovering the space.
Matthew
> On Jul 14, 2015, at 12:32 PM, Antonio Teixeira <eagle.anto...@gmail.com>
> wrote:
>
> Hello,
>
> We have been migrating our Riak Database to another infrastructure through a
> "streaming" process and right now we should have somewhere around 2Gb of free
> space the Hard Disk, however those 2Gb are still being used by Riak. After
> some research I believe the problem is the Objects are only being marked for
> deletion and not actually deleted at runtime. What we need is a way to
> aggressively deleted those keys or some way to force Riak to delete those
> marked keys and subsequently release the Disk Space. The Riak version we are
> using is v2.0.2
> _______________________________________________
> 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
