Steve, Kyle, In order to track it down, I'd like to be able to reproduce this issue. Can you provide some minimal Java code to reproduce, from an empty Riak cluster? Please include any changes to the Riak app.config as well.
Some things to think about in writing code to reproduce: * Are you connecting to a single node? Using a load-balancer? Using RJC to connect to multiple nodes? * Are you overriding any default bucket properties? Either for a specific bucket or changing the defaults in the app.confg? Kyle, are you seeing the same issue where some small number ~200 / 20K are remaining, or a smaller/larger percent? Thanks, Reid Draper On May 23, 2012, at 4:43 PM, Steve Warren wrote: > Whew! I was afraid I was the only one! > > On Wed, May 23, 2012 at 1:37 PM, Kyle Kingsbury <ap...@aphyr.com> wrote: > On 05/23/2012 01:08 PM, Steve Warren wrote: > I'm seeing this pretty consistently and have no explanation for it. I > delete a large number of keys (20k to 100k), but when I then search on > the keys ($key/0/g) anywhere from 0-200 or so of the deleted keys show > up in the results. It doesn't matter how long I wait after completing > the deletion step, the keys stay in the list until I try to access the > object and then it goes away. I'm using 1.1.2 and the riak-java client, > and getting no errors on the deletion step. > > We're *also* seeing this problem: residual keys that persist in 2I for days > after deletion, and disappear on get. Using Java client, Riak 1.1.1. If you > figure this out I'd like to hear about it. > > --Kyle > > _______________________________________________ > 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
