[
https://issues.apache.org/jira/browse/SOLR-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973317#comment-13973317
]
Rich Mayfield commented on SOLR-5991:
-------------------------------------
I'm not sure which approach would be easier to implement at this point.
Something else to consider and discuss is what a "success" return from the API
call means - maybe this might help in choosing an approach.
I would hope that getting a "success" return means that leadership (whether
given or taken) completed through the election process. If we tell a core to
give up leadership, then we only return once leadership was successfully picked
up by another core. Likewise, if we gell a core to take leadership, then we get
a return once that core has leadership.
Ideally, I don't want to make the call and then have to follow up with
subsequent calls to see if the leader election process played out.
> SolrCloud: Add API to move leader off a Solr instance
> -----------------------------------------------------
>
> Key: SOLR-5991
> URL: https://issues.apache.org/jira/browse/SOLR-5991
> 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
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
