Riak2.0 with Solr Search: index on one node contains not all entries

Zeeshan Lakhani zlakhani at basho.com
Wed Mar 25 10:10:44 EDT 2015

Hello Michael,

First off, that section of the docs related to search index repair that you linked to is not referring to Riak Search 2.0 with Solr, and the link itself is actually pointing to Riak 1.4.7. We’ll update them accordingly for the current incarnation of Riak Search (for the 2.0 series).

Just to be sure, does your custom schema include the required fields, as mentioned in the docs: http://docs.basho.com/riak/latest/dev/advanced/search-schema/#Custom-Schemas? <http://docs.basho.com/riak/latest/dev/advanced/search-schema/#Custom-Schemas?> Are these Riak nodes joined? What’s your ring size, n_val value?

How are you querying the Solr nodes to know which node has the data and which one doesn't? Coverage is R=1, so you would be getting a different number on some search queries (using the standard /search/query/<index_name>?...) if its only on one of the Solr cores.

Can you also post me a screenshot of your search AAE exchanges, e.g. `riak-admin search aae-status`? You could look at this thread, http://lists.basho.com/pipermail/riak-users_lists.basho.com/2015-March/016926.html <http://lists.basho.com/pipermail/riak-users_lists.basho.com/2015-March/016926.html>, for answers on how to perform read-repair/repair the AAE tree.


Zeeshan Lakhani
programmer | 
software engineer at @basho | 
org. member/founder of @papers_we_love | paperswelove.org
twitter => @zeeshanlakhani

> On Mar 25, 2015, at 6:42 AM, Michael Weibel <michael.weibel at gmail.com> wrote:
> Hi all,
> I have on a test environment two riak nodes and each of them has solr activated which index 3 buckets using a custom schema.
> After testing a bit back and forth, I have the case that on one solr node, an entry is not in the index (I know in which node though). 
> Fetching the specific key in the bucket works however, both nodes have the respective entry.
> 1) How can this happen? I don't see any error/warning in the logs (neither solr nor riak logs). 
> 2) Is there a possibility to fix this without having to do e.g. a PUT on the specific key with the same content in order to update it?
> I tried to run a repair on the failing node using the guide: http://docs.basho.com/riak/1.4.7/ops/running/recovery/repairing-indexes/#Repairing-Search-Indexes <http://docs.basho.com/riak/1.4.7/ops/running/recovery/repairing-indexes/#Repairing-Search-Indexes>
> When running the repair command on the partitions I received, it gave me however a [{<PartitionId>, down}, {...}] response, which gives me an uncomfortable feeling, but I didn't really figure out yet what this means exactly. 
> Thanks a lot for your help :)
> Best,
> Michael
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20150325/57f5a4cd/attachment-0002.html>

More information about the riak-users mailing list