Yokozuna inconsistent search results

Oleksiy Krivoshey oleksiyk at gmail.com
Fri Mar 11 07:38:12 EST 2016


Here are two consequent requests, one returns 30118 keys, another 37134

<?xml version="1.0" encoding="UTF-8"?>
<response>
  <lst name="responseHeader">
    <int name="status">0</int>
    <int name="QTime">6</int>
    <lst name="params">
      <str name="10.0.1.3:8093">_yz_pn:92 OR _yz_pn:83 OR _yz_pn:71 OR
_yz_pn:59 OR _yz_pn:50 OR _yz_pn:38 OR _yz_pn:17 OR _yz_pn:5</str>
      <str name="10.0.1.2:8093">_yz_pn:122 OR _yz_pn:110 OR _yz_pn:98 OR
_yz_pn:86 OR _yz_pn:74 OR _yz_pn:62 OR _yz_pn:26 OR _yz_pn:14 OR
_yz_pn:2</str>
      <str name="shards">
10.0.1.1:8093/internal_solr/chunks_index,10.0.1.2:8093/internal_solr/chunks_index,10.0.1.3:8093/internal_solr/chunks_index,10.0.1.4:8093/internal_solr/chunks_index,10.0.1.5:8093/internal_solr/chunks_index
</str>
      <str name="q">_yz_rb:0dmid2ilpyrfiuaqtvnc482f1esdchb5.chunks</str>
      <str name="10.0.1.5:8093">(_yz_pn:124 AND (_yz_fpn:124 OR
_yz_fpn:123)) OR _yz_pn:116 OR _yz_pn:104 OR _yz_pn:80 OR _yz_pn:68 OR
_yz_pn:56 OR _yz_pn:44 OR _yz_pn:32 OR _yz_pn:20 OR _yz_pn:8</str>
      <str name="10.0.1.1:8093">_yz_pn:113 OR _yz_pn:101 OR _yz_pn:89 OR
_yz_pn:77 OR _yz_pn:65 OR _yz_pn:53 OR _yz_pn:41 OR _yz_pn:29</str>
      <str name="10.0.1.4:8093">_yz_pn:127 OR _yz_pn:119 OR _yz_pn:107 OR
_yz_pn:95 OR _yz_pn:47 OR _yz_pn:35 OR _yz_pn:23 OR _yz_pn:11</str>
      <str name="rows">0</str>
    </lst>
  </lst>
  <result maxScore="6.364349" name="response" numFound="30118"
start="0"></result>
</response>

------


<?xml version="1.0" encoding="UTF-8"?>
<response>
  <lst name="responseHeader">
    <int name="status">0</int>
    <int name="QTime">10</int>
    <lst name="params">
      <str name="10.0.1.3:8093">_yz_pn:100 OR _yz_pn:88 OR _yz_pn:79 OR
_yz_pn:67 OR _yz_pn:46 OR _yz_pn:34 OR _yz_pn:25 OR _yz_pn:13 OR
_yz_pn:1</str>
      <str name="10.0.1.2:8093">(_yz_pn:126 AND (_yz_fpn:126 OR
_yz_fpn:125)) OR _yz_pn:118 OR _yz_pn:106 OR _yz_pn:94 OR _yz_pn:82 OR
_yz_pn:70 OR _yz_pn:58 OR _yz_pn:22 OR _yz_pn:10</str>
      <str name="shards">
10.0.1.1:8093/internal_solr/chunks_index,10.0.1.2:8093/internal_solr/chunks_index,10.0.1.3:8093/internal_solr/chunks_index,10.0.1.4:8093/internal_solr/chunks_index,10.0.1.5:8093/internal_solr/chunks_index
</str>
      <str name="q">_yz_rb:0dmid2ilpyrfiuaqtvnc482f1esdchb5.chunks</str>
      <str name="10.0.1.5:8093">_yz_pn:124 OR _yz_pn:112 OR _yz_pn:76 OR
_yz_pn:64 OR _yz_pn:52 OR _yz_pn:40 OR _yz_pn:28 OR _yz_pn:16 OR
_yz_pn:4</str>
      <str name="10.0.1.1:8093">_yz_pn:121 OR _yz_pn:109 OR _yz_pn:97 OR
_yz_pn:85 OR _yz_pn:73 OR _yz_pn:61 OR _yz_pn:49 OR _yz_pn:37</str>
      <str name="10.0.1.4:8093">_yz_pn:115 OR _yz_pn:103 OR _yz_pn:91 OR
_yz_pn:55 OR _yz_pn:43 OR _yz_pn:31 OR _yz_pn:19 OR _yz_pn:7</str>
      <str name="rows">0</str>
    </lst>
  </lst>
  <result maxScore="6.364349" name="response" numFound="37134"
start="0"></result>
</response>

On 11 March 2016 at 12:05, Oleksiy Krivoshey <oleksiyk at gmail.com> wrote:

> So event when I fixed 3 documents which caused AAE errors,
> restarted AAE with riak_core_util:rpc_every_member_ann(yz_entropy_mgr,
> expire_trees, [], 5000).
> waited 5 days (now I see all AAE trees rebuilt in last 5 days and no AAE
> or Solr errors), I still get inconsistent num_found.
>
> For a bucket with 30,000 keys each new search request can result in
> difference in num_found for over 5,000.
>
> What else can I do to get consistent index, or at least not a 15%
> difference.
>
> I even tried to walk through all the bucket keys and modifying them in a
> hope that all Yokozuna instances in a cluster will pick them up, but no
> luck.
>
> Thanks!
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20160311/6a8cb213/attachment-0002.html>


More information about the riak-users mailing list