This same thing is happening to me, where both $bucket index and my own custom indexes are returning keys that have been deleted and I can’t remove them. I am hoping there is a way to fix this as it is causing significant problems for us in production. It seems to be happening with some frequency, and every once in a while an index will just go bad completely and either return subsets of what it should return (even with a healthy cluster), or keys that have been deleted.
I had a case yesterday where $bucket was returning 6 keys that my custom all-inclusive index wasn’t returning. They all produced 404s when I tried to retrieve a value. I was hoping read repair would repair the index when a 404 occurred, or at least AAE might pick it up, but as it stands now, is there any way corrupted indexes like this can ever get back to normal? Sean On Nov 4, 2013, at 9:44 AM, Evan Vigil-McClanahan <[email protected]> wrote: > Hi Toby. > > It's possible, since they're stored separately, that the objects were > deleted but the indices were left in place because of some error (e.g. > the operation failed for some reason between the object removal and > the index removal). One of the things on the feature list for the > next release is AAE of index values, which should take care of this > case. This is really rare, but not unknown. It'd be interesting to > know how you ended up with so many. > > In the mean time, the only way I can think of to get rid of them > (other than deleting them from the console, which would require taking > nodes down and a lot of manual effort), would be to write another > value that would have the same index, then delete it, which should > normally succeed. > > I'll ask around to see if there is anything that might work better. > > On Sun, Nov 3, 2013 at 7:40 PM, Toby Corkindale > <[email protected]> wrote: >> On 01/11/13 14:04, Toby Corkindale wrote: >>> >>> Hi, >>> I have around 5000 keys which just won't die. >>> No matter how many times I delete them, they still show up in the 2i >>> $bucket=_ index. >>> >>> Actually attempting to retrieve the keys results in a not-found - even >>> >>> if I've requested that tombstones be returned. >>> >>> I'm interested to know what is going on here? >> >> >> Anyone? >> >> Should I report this as a bug against 1.4.2? >> >> >> _______________________________________________ >> 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 _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
