You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Georg Henzler (Jira)" <ji...@apache.org> on 2020/07/06 15:03:00 UTC
[jira] [Comment Edited] (FELIX-6295) Introduce initial delay for
asynchronous health checks with interval
[ https://issues.apache.org/jira/browse/FELIX-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152074#comment-17152074 ]
Georg Henzler edited comment on FELIX-6295 at 7/6/20, 3:02 PM:
---------------------------------------------------------------
Please see test the setup from comment https://issues.apache.org/jira/browse/FELIX-6292?focusedCommentId=17152070&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17152070 using a cron expression for HealthCheckMonitor only.
bq. executed immediately first
Generally when using cron expressions, there should only be executions that satisfy the cron expression, e.g. "0 15 10 * * ?" will not fire on bundle start in the after noon but way for the next "compliant time" at 10.15am the next day.
Why introduce an additional property (which would require to bump the API version) when for those cases, just a cron expression can be used? (now that we have it for all setups...)
was (Author: henzlerg):
Please see test the setup from comment https://issues.apache.org/jira/browse/FELIX-6292?focusedCommentId=17152070&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17152070 using a cron expression for HealthCheckMonitor only.
bq. executed immediately first
Generally when using cron expressions, there should only be executions that satisfy the cron expression, e.g. "0 15 10 * * ?" will not fire on bundle start in the after noon but way for the next "compliant time" at 10.15am the next day.
> Introduce initial delay for asynchronous health checks with interval
> --------------------------------------------------------------------
>
> Key: FELIX-6295
> URL: https://issues.apache.org/jira/browse/FELIX-6295
> Project: Felix
> Issue Type: New Feature
> Components: Health Checks
> Reporter: Amit Mondal
> Priority: Minor
> Labels: pull-request-available
>
> Currently we can schedule health checks having different intervals but we cannot configure the initial delay of the health check execution. It is currently set to be executed immediately first and then it is executed according to the configured interval. Consumers might also need to delay the first execution at a later time - not immediately. That's why it would be beneficial to introduce _*initialDelayForIntervalInSec*_ attribute in _*Async*_ component type annotation (which can be set to 0 as default since it is the current behavior). If consumers need, they would still be able to configure it accordingly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)