You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2018/04/13 00:30:00 UTC

[jira] [Commented] (SOLR-12219) Autoscaling trigger to forceleader

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

Erick Erickson commented on SOLR-12219:
---------------------------------------

This seems dangerous. This could potentially lead to loss of data and the sysadmins have no clue that it fired. At least if they have to send it manually then they have some chance of remembering why data disappeared.

> Autoscaling trigger to forceleader
> ----------------------------------
>
>                 Key: SOLR-12219
>                 URL: https://issues.apache.org/jira/browse/SOLR-12219
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: AutoScaling
>            Reporter: Varun Thacker
>            Priority: Major
>
> In a scenario where a shard doesn't have a leader for an extended period of time, it would be nice if we can configure a trigger to fire a FORCELEADER API call
>  
> FORCELEADER is the first step an ops person would fire today to come out of the leaderless shard scenario and if this could be automated then it would be useful for teams
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org