[
https://issues.apache.org/jira/browse/SOLR-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502612#comment-13502612
]
Po Rui commented on SOLR-4105:
------------------------------
It cause the load balance for search. it means your search requests may not
handle by instance A even you send them to A. more detail:
1 slice with 2 shards refer to A(leader) and B(replica).when you send a search
request to A it assign to A or B randomly by A.
so the situation in
http://lucene.472066.n3.nabble.com/Weird-Behaviour-on-Solr-5x-SolrCloud-td4021219.html
is normal.
The problem is the restarted B doesn't recovery to the leader A. it may be a
bug or cause a uncompleted feature due to the recovering base on file level and
commit version
> SolrCloud - Restarting a Solr Node Causes Random Results
> ---------------------------------------------------------
>
> Key: SOLR-4105
> URL: https://issues.apache.org/jira/browse/SOLR-4105
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.0
> Environment: Linux
> Reporter: Deniz Durmus
> Labels: solrcloud, solrindex
>
> For Brief description, basically restarting a Solr instance in cloud causes a
> weird behavior, it shows results, randomly from the instance itself and then
> the leader, which causes seeing 0 results and then correct amount of results.
> In addition to this, the restarted node wont be sync'ed with the rest of the
> cloud, unless you delete the data folder's contents before restarting.
> For more details, you can follow the thread here:
> You can see the details and flow of the issue here:
> http://lucene.472066.n3.nabble.com/Weird-Behaviour-on-Solr-5x-SolrCloud-td4021219.html
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
