lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramkumar Aiyengar (JIRA)" <>
Subject [jira] [Commented] (SOLR-5991) SolrCloud: Add API to move leader off a Solr instance
Date Fri, 18 Apr 2014 10:12:15 GMT


Ramkumar Aiyengar commented on SOLR-5991:

Re: (1) : Ideally you want the avoid_responsibility rule to do just that,  I.e. avoid that.
In the off chance that the external client ends up doing that to all replicas of the shard,
it should still be considered for leadership. This just makes it safer for the client. If
not, it should at least be possible to do this only if safe, I.e. without a 'force' option,
the node should reject a request to avoid responsibility if it's the only responsible node

> SolrCloud: Add API to move leader off a Solr instance
> -----------------------------------------------------
>                 Key: SOLR-5991
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.7.1
>            Reporter: Rich Mayfield
> Common maintenance chores require restarting Solr instances.
> The process of a shutdown becomes a whole lot more reliable if we can proactively move
any leadership roles off of the Solr instance we are going to shut down. The leadership election
process then runs immediately.
> I am not sure what the semantics should be (either accomplishes the goal but one of these
might be best):
> * A call to tell a core to give up leadership (thus the next replica is chosen)
> * A call to specify which core should become the leader

This message was sent by Atlassian JIRA

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

View raw message