[
https://issues.apache.org/jira/browse/SOLR-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731796#comment-16731796
]
ASF subversion and git services commented on SOLR-13082:
--------------------------------------------------------
Commit 5327bae866dffe524ce5e6bc34fcbeaf7a2b9c9b in lucene-solr's branch
refs/heads/branch_7x from Shalin Shekhar Mangar
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5327bae ]
SOLR-13082: A trigger that creates trigger events more frequently than the cool
down period can starve other triggers.
This is mitigated to some extent by randomly choosing the trigger to resume
after cool down. It is recommended that scheduled triggers not be used for very
frequent operations to avoid this problem.
(cherry picked from commit 5016959ce8c1eed9d354822f01edc4b509e4aa9d)
> A trigger that creates trigger events more frequently than the cool down
> period can starve other triggers
> ---------------------------------------------------------------------------------------------------------
>
> Key: SOLR-13082
> URL: https://issues.apache.org/jira/browse/SOLR-13082
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Reporter: Shalin Shekhar Mangar
> Priority: Major
> Fix For: master (8.0), 7.7
>
> Attachments: SOLR-13082.patch
>
>
> A trigger that creates frequent events (such as ScheduledTrigger) with period
> less than the cool down period can starve all other triggers. This is because
> we execute triggers in the same order each time so if the scheduled trigger
> happens to be the first in the list then after every cool down period, the
> scheduled trigger can create another event and the cycle repeats.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
