[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=16436683#comment-16436683 ] Shawn Heisey commented on SOLR-12219: - Would that force just be an election, or would it be forcing a specific replica to the leader role? If it's an election, does that tend to pick the system with the most recent changes? The best option is to not ever get into a situation where there's no leader. If we have documented situations where that happens, can we make changes to keep it from happening in those situations? > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[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=16436596#comment-16436596
]
Varun Thacker commented on SOLR-12219:
--
You would need to explicitly create a trigger using an API . A user would
explicitly configure this .
Not sure if the syntax is correct but one would setup something like this with
autoscaling:
{code:java}
"set-trigger": {
"name" : "leaderless_shard_trigger",
"event" : "leaderLost",
"waitFor" : "300s",
"enabled" : true,
"actions" : [
{
"name" : "compute_plan",
"class": "solr.ComputePlanAction"
},
{
"name" : "execute_plan",
"class": "solr.ExecutePlanAction"
}
]
}
}{code}
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
