I wonder if you have some keys that are hanging around on one of the N
partitions but are deleted elsewhere (and the tombstones reaped?). 2i uses
coverage which is essentially r=1 on a covering set of vnodes. But you think
read-repair/AAE would bring convergence, so it is perplexing. I wonder if
@Matthew
No, db activity was very low at this time, and keys returned by this
queries was deleted long time ago ( some of them at Dec 2015 )
I got this issue when proceed maintenance task which touch all keys in
DB, list all keys by /keys?keys=true query, read, upgrade, save.
We have some log
Is the database being actively modified during your queries?
Queries can lock down a "snapshot" within leveldb. The query operation can
return keys that existed at the time of the snapshot, but have been
subsequently deleted by normal operations.
In such a case, the query is correct in givin
It could be the logs need to be repaired. Or inadvertently multiple keys
have been added under the same index.
It's unlikely your whole database is corrupt
On Tuesday, March 8, 2016, Alexander Popov wrote:
> Noticied that sometimes 2i query and all keys requesrs returns extra
> records ~2% of al
Noticied that sometimes 2i query and all keys requesrs returns extra
records ~2% of all records.
When call this items by get request after, it returns 404 and after that
key stops to returns in 2i and keys requests.
Does it normally or my database is corrupted?
__
