jwest at basho.com
Tue Jun 10 12:14:56 EDT 2014
If you can successfully read the key(s)*, the simplest solution would be to
do a typical read/write cycle to overwrite the siblings with a single value
(merging the siblings would be dependent on your application).
If that is not feasible let us know and we can work through a way to delete
the object directly from the backend.
In either case, the backend will eventually, during merging/compaction,
reclaim the space for the version of the object with many siblings.
* Riak, depending on your environment/network/etc, may not handle objects
that large very well. It may help to raise the "zdbbl" in your vm.args.
On Tue, Jun 10, 2014 at 8:46 AM, Alain Rodriguez <alain at uber.com> wrote:
> Hi all,
> I had a bug in my ingestion code that caused sibling explosion in a
> specific bucket. I have temporarily turned off allow_mult=true until that
> bug is fixed. Is there a way to remove all of the siblings on those
> existing massive objects (up to 10MB) now that allow_mult is false? Will
> Riak do that automatically?
> riak-users mailing list
> riak-users at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users