[
https://issues.apache.org/jira/browse/SOLR-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725509#comment-13725509
]
Isaac Hebsh commented on SOLR-5092:
-----------------------------------
Hi Ryan, you're absolutely right. SOLR-4449 exactly addresses my issue. if
repFactor is 2, we suggest the same solution.. :)
On the other hand, I didn't understand your response about the case when
distributedProcess might address different replicas on different phases, if one
replica stop responding.
> Send shard request to multiple replicas
> ---------------------------------------
>
> Key: SOLR-5092
> URL: https://issues.apache.org/jira/browse/SOLR-5092
> Project: Solr
> Issue Type: Improvement
> Components: clients - java, SolrCloud
> Affects Versions: 4.4
> Reporter: Isaac Hebsh
> Priority: Minor
> Labels: distributed, performance, shard, solrcloud
> Attachments: SOLR-5092.patch
>
>
> We have a case on a SolrCloud cluster. Queries takes too much QTime, due to a
> randomly slow shard request. In a noticeable part of queries, the slowest
> shard consumes more than 4 times qtime than the average.
> Of course, deep inspection of the performance factor should be made on the
> specific environment.
> But, there is one more idea:
> If shard request will be sent to all of the replicas of each shard, the
> probability of all the replicas of the same shard to be the slowest is very
> small. Obviously cluster works harder, but on a (very) low qps, it might be
> OK.
--
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]
