[
https://issues.apache.org/jira/browse/SOLR-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706450#comment-15706450
]
Mark Miller commented on SOLR-9811:
-----------------------------------
I don't think this will really add anything on top of the force leader api - if
you cannot force a leader (already a data loss dangerous last resort
operation), something like this has extremely little, if any, chance of helping
the situation.
Regardless, rather than exposing something so internal, the force leader api
should probably be bulked up to try even more than it does now if something is
missing.
> Make it easier to manually execute overseer commands
> ----------------------------------------------------
>
> Key: SOLR-9811
> URL: https://issues.apache.org/jira/browse/SOLR-9811
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Mike Drob
>
> Sometimes solrcloud will get into a bad state w.r.t. election or recovery and
> it would be useful to have the ability to manually publish a node as active
> or leader. This would be an alternative to some current ops practices of
> restarting services, which may take a while to complete given many cores
> hosted on a single server.
> This is an expert operator technique and readers should be made aware of
> this, a.k.a. the "I don't care, just get it running" approach.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
