[jira] [Commented] (SOLR-9811) Make it easier to manually execute overseer commands

["Scott Blum (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715835#comment-15715835 ] 

Scott Blum commented on SOLR-9811:
----------------------------------

REQUESTRECOVERY did not work:

{code}
2016-12-02 18:03:02.611 ERROR (recoveryExecutor-3-thread-10-processing-n:10.240.0.69:8983_solr x:24VFQ_shard1_replica0 s:shard1 c:24VFQ r:core_node1) [c:24VFQ s:shard1 r:core_node1 x:24VFQ_shard1_replica0] o.a.s.c.RecoveryStrategy Error while trying to recover. core=24VFQ_shard1_replica0:org.apache.solr.common.SolrException: Cloud state still says we are leader.
        at org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:320)
{code}

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org