[
https://issues.apache.org/jira/browse/SOLR-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335355#comment-16335355
]
ASF subversion and git services commented on SOLR-11747:
--------------------------------------------------------
Commit d61aec090454eeea0d498850c1dabbda5fbfc5e0 in lucene-solr's branch
refs/heads/branch_7x from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d61aec0 ]
SOLR-11747: Fixed note in upgrade section
(cherry picked from commit e16da35)
> 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
> Priority: Major
> Fix For: master (8.0), 7.3
>
> Attachments: SOLR-11747.patch, SOLR-11747.patch
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
