lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Thacker (JIRA)" <>
Subject [jira] [Commented] (SOLR-9090) solrj CloudSolrClient: add directUpdatesToLeadersOnly support
Date Thu, 04 Aug 2016 08:15:20 GMT


Varun Thacker commented on SOLR-9090:

Hi Christine,

Just curious - Why shouldn't directUpdatesToLeadersOnly be the default behaviour? 

If at a time of an update there are no leaders then won't the request fail anyways? 

> solrj CloudSolrClient: add directUpdatesToLeadersOnly support
> -------------------------------------------------------------
>                 Key: SOLR-9090
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrJ
>            Reporter: Christine Poerschke
>            Assignee: Christine Poerschke
>            Priority: Minor
>             Fix For: 6.2, master (7.0)
>         Attachments: SOLR-9090.patch, SOLR-9090.patch
> solrj CloudSolrClient: add directUpdatesToLeadersOnly support
> (Marvin Justice, Christine Poerschke)
> Proposed change:
> * Addition of a {{directUpdatesToLeadersOnly}} flag to allow clients to request that
direct updates be sent to the shard leaders and only to the shard leaders.
> Motivation:
> * In a scenario where there is temporarily no shard leader the update request will 'fail
fast' allowing the client to handle retry logic.
> Related tickets:
> * SOLR-6312 concerns the ((currently) no longer used) {{updatesToLeaders}} flag. The
updatesToLeaders logic however appears to be slightly different from the proposed directUpdatesToLeadersOnly
logic: {{updatesToLeaders}} indicates that sending to leaders is preferred but not mandatory
whereas {{directUpdatesToLeadersOnly}} mandates sending to leaders only.

This message was sent by Atlassian JIRA

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

View raw message