You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2014/07/30 16:07:39 UTC
[jira] [Commented] (SLING-3744) Schedule execution of HCs based on
a crontab-like service property
[ https://issues.apache.org/jira/browse/SLING-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14079303#comment-14079303 ]
Bertrand Delacretaz commented on SLING-3744:
--------------------------------------------
I have also mentioned the new service property at http://sling.apache.org/documentation/bundles/sling-health-check-tool.html
> Schedule execution of HCs based on a crontab-like service property
> ------------------------------------------------------------------
>
> Key: SLING-3744
> URL: https://issues.apache.org/jira/browse/SLING-3744
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
> Reporter: Georg Henzler
> Assignee: Bertrand Delacretaz
> Fix For: Health Check Core 1.1.2, Health Check samples 1.0.6
>
> Attachments: SLING-3744-async-health-checks-using-configuration.patch
>
>
> Make HCs sync/async behaviour configurable via service property "hc.async.cronExpression". This allows operations to decide whether a check should be run synchronously or asynchronously (e.g. could be different for TEST and PROD). For checks that always have to run asynchronously, it simplifies the implementation significantly (see org.apache.sling.hc.samples.impl.AsyncHealthCheckSample from patch).
> The logic for registering/deregistering jobs for async HCs is in AsyncHealthCheckExecutor, HealthCheckExecutorImpl has only changed slightly in a way that it retrieves the results from AsyncHealthCheckExecutor for checks configured to be asynchronous.
--
This message was sent by Atlassian JIRA
(v6.2#6252)