Hey Alain, 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. Cheers, Jordan * 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 <[email protected]> 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? > > Cheers, > > Alain > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
