Yokozuna - inconsistent number of documents found for the same query
oleksiyk at gmail.com
Tue Dec 2 01:49:08 EST 2014
There are no errors, 'search aae-status' shows that all trees have already
been created and synced.
When I first noticed this issue I was running a dev setup (single node) and
had about 500 keys in total. I waited over 7 days and still was
experiencing this issue. During these 7 days the AAE continued to repair
keys according to logs, but 'search aae-status' was showing that all trees
were already synced (and re-synced).
I then created a test Riak setup (again single node) with just 20 keys. I
replicated the problem, waited for 'aae-status' to show all synced trees
(about 2 days) and wrote about the problem here. During these tests I
_sometimes_ received full set of documents as stated in my original email -
for me that was an indication that all keys have already been repaired.
Now, 6 days after that I can no longer replicate it - I always get full set
of documents.The last message from AAE key_exchange was logged yesterday (5
days after test setup was created).
So it seems that for 20 keys it finally started working after 5-6 days.
On 2 December 2014 at 06:57, Ryan Zezeski <ryan at zinascii.com> wrote:
> Eric Redmond writes:
> > This is a known issue, and we're still working on a fix.
> > https://github.com/basho/yokozuna/issues/426
> I don't see how this issue is related to Oleksiy's problem. There is no
> mention of removing or adding nodes. I think the key part of Oleksiy's
> report is the association of an index _after_ data had already been
> written. That data is sometimes missing. These two issues could be
> related but I don't see anything in that GitHub report to indicate why.
> > On Nov 29, 2014, at 9:26 AM, Oleksiy Krivoshey <oleksiyk at gmail.com>
> >> 1. Create a bucket, insert some keys (10 keys - KeysA)
> >> 2. Create Yokozuna Index, associate it with the bucket
> >> 3. Add or update some new keys in the bucket (10 keys - KeysB)
> >> 4. Wait for Search AAE to build and exchange the trees
> >> Now when I issue a search query I will always get all 10 KeysB but a
> random amount of KeysA, for example the same query repeated 5 times may
> >> 10 KeysB + 2 KeysA
> >> 10 KeysB + 0 KeysA
> >> 10 KeysB + 7 KeysA
> >> 10 KeysB + 1 KeysA
> >> 10 KeysB + 10 KeysA
> Are there any errors in the logs? Does the count go up if you wait
> longer? What does `riak-admin search aae-status` show?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users