[ 
https://issues.apache.org/jira/browse/SOLR-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924127#comment-13924127
 ] 

Maxim Novikov commented on SOLR-5821:
-------------------------------------

PS Regarding "misunderstanding" and stuff like that... This behavior is 
unexpected for me. As I wrote, I have a load balancer that redirects queries to 
Solr's replicas having the only shard, and running the same query (even not 
specifying any additional parameters), I expect to retrieve the same results. 
You can tell anything about how Solr is implemented internally, but from the 
perspective of Solr's user (search's user) I should not care about that at all. 
That was the point. If you disagree and think that this is sort of a "feature", 
not a bug/issue, that is still good to keep this stuff in JIRA. The other 
people who face the same issue will be able to find it, read Solr developers' 
responses, and judge for themselves whether this "feature" fits the search 
solution they want to get or not.

> Search inconsistency on SolrCloud replicas
> ------------------------------------------
>
>                 Key: SOLR-5821
>                 URL: https://issues.apache.org/jira/browse/SOLR-5821
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.6.1
>         Environment: SolrCloud:
> 1 shard, 2 replicas
> Both instances/replicas have identical hardware/software:
> CPU(s): 4
> RAM: 8Gb
> HDD: 100Gb
> OS: CentOS 6.5
> ZooKeeper 3.4.5
> Tomcat 8.0.3
> Solr 4.6.1
> Servers are utilized to run Solr only.
>            Reporter: Maxim Novikov
>            Priority: Critical
>              Labels: cloud, inconsistency, replica, search
>
> We use the following infrastructure:
> SolrCloud with 1 shard and 2 replicas. The index is built using 
> DataImportHandler (importing data from the database). The number of items in 
> the index can vary from 100 to 100,000,000.
> After indexing part of the data (not necessarily all the data, it is enough 
> to have a small number of items in the search index), we can observe that 
> Solr instances (replicas) return different results for the same search 
> queries. I believe it happens because some of the results have the same 
> scores, and Solr instances return those in a random order.
> PS This is a critical issue for us as we use a load balancer to scale Solr 
> through replicas, and as a result of this issue, we retrieve various results 
> for the same queries all the time. They are not necessarily completely 
> different, but even a couple of items that differ is a deal breaker.
> The expected behaviour would be to always get identical results for the same 
> search queries from all replicas. Otherwise, this "cloud" thing works just 
> unreliably.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to