Hmmm, if all the nodes for a shard are down, shards.tolerant=true
shouldn't be slow unless there's some kind of bug. Solr should be
smart enough not to wait for a timeout. So I'm a bit surprised by that
statement, how sure of it are you? Do you have a test case?
bq: but this is slow and dont gives all results.
Well, you can _never_ have all results if all the replicase for a
shard are down, so the second part of that statement is just the way
the system _has_ to work.
SolrCloud is a wonderful system. The HA/DR handling is predicated upon
at least one member of each shard being available. When you violate
that expectation you have to pay the price of at least incomplete
responses.
Best,
Erick
On Fri, Sep 12, 2014 at 2:33 AM, Amey Jadiye
<ameyjad...@codeinventory.com> wrote:
> Just a dumb question but how can i make solr cloud fault tolerant for queries
> ? why i am asking this question because, i have 12 different physical server
> and i am running 12 solr shards on that, whenever any one of them is going
> down because of any reason it gives me below error, i have 3 zookeeper for 12
> servers all are leader and no replica for this solr cloud.
> I have option of using shards.tolerant=true but this is slow and dont gives
> all results.
> Best,Amey
> {
> "responseHeader": {
> "status": 503,
> "QTime": 7,
> "params": {
> "sort": "last_modified asc",
> "indent": "true",
> "q": "+links:[* TO *]",
> "_": "1410512274068",
> "wt": "json"
> }
> },
> "error": {
> "msg": "no servers hosting shard: ",
> "code": 503
> }
> }
