[
https://issues.apache.org/jira/browse/SOLR-10602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-10602:
-----------------------------------------
Fix Version/s: (was: 7.0)
7.1
master (8.0)
> Triggers should be able to restore state from old instances when taking over
> ----------------------------------------------------------------------------
>
> Key: SOLR-10602
> URL: https://issues.apache.org/jira/browse/SOLR-10602
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Labels: autoscaling
> Fix For: master (8.0), 7.1
>
> Attachments: SOLR-10602.patch, SOLR-10602.patch
>
>
> Currently if a user modifies a trigger then the old trigger is closed and
> unscheduled and replaced with a new trigger instance with updated properties.
> However, this loses the intermediate state that the trigger may have been
> tracking. For example, say there is a trigger for NodeAdded event with
> waitFor=5s and a new node is added to the cluster. While the trigger is
> waiting for 5s before firing, the user modifies the trigger to change the
> waitFor=2s. Doing this today will erase the state of the old trigger and the
> new trigger will never fire for the newly added node.
> We need to be able to restore state from old trigger instance before
> replacing it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
