lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <>
Subject [jira] [Commented] (SOLR-13445) Preferred replicas on nodes with same system properties as the query master
Date Fri, 03 May 2019 16:01:00 GMT


Andrzej Bialecki  commented on SOLR-13445:

The bug in {{SolrClientNodeStateProvider}} should be fixed in other active branches too, regardless
of this improvement.

> Preferred replicas on nodes with same system properties as the query master
> ---------------------------------------------------------------------------
>                 Key: SOLR-13445
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Cao Manh Dat
>            Assignee: Cao Manh Dat
>            Priority: Major
>         Attachments: SOLR-13445.patch
> Currently, Solr chooses a random replica for each shard to fan out the query request.
However, this presents a problem when running Solr in multiple availability zones.
> If one availability zone fails then it affects all Solr nodes because they will try to
connect to Solr nodes in the failed availability zone until the request times out. This can
lead to a build up of threads on each Solr node until the node goes out of memory. This results
in a cascading failure.
> This issue try to solve this problem by adding
> * another shardPreference param named {{node.sysprop}}, so the query will be routed to
nodes with same defined system properties as the current one.
> * default shardPreferences on the whole cluster, which will be stored in {{/clusterprops.json}}.
> * a cacher for fetching other nodes system properties whenever /live_nodes get changed.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message