You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2017/12/12 08:07:00 UTC
[jira] [Updated] (SOLR-11747) Pause triggers until actions finish
executing and the cool down period expires
[ https://issues.apache.org/jira/browse/SOLR-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar updated SOLR-11747:
-----------------------------------------
Issue Type: Sub-task (was: Improvement)
Parent: SOLR-9735
> Pause triggers until actions finish executing and the cool down period expires
> ------------------------------------------------------------------------------
>
> Key: SOLR-11747
> URL: https://issues.apache.org/jira/browse/SOLR-11747
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: master (8.0), 7.3
>
>
> Currently, the cool down period is a fixed period during which events generated from triggers aren't accepted. The cool down starts after actions performed by a previous event finish. But it doesn't protect against triggers acting on intermediate cluster state during the time the actions are executing. Events can still be created and persisted to ZK and will be executed serially once the cool down finishes.
> To protect against, this I intend to modify the behaviour of the system to pause all triggers from execution between the start of actions and end of cool down period. The triggers will be resumed after the cool down period expires.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org