[
https://issues.apache.org/jira/browse/SLING-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-3744.
----------------------------------------
Resolution: Fixed
Fix Version/s: Health Check samples 1.0.6
Health Check Core 1.1.2
Thanks very much for this contribution, I have applied your patch in
http://svn.apache.org/r1614655 with a few tweaks in
http://svn.apache.org/r1614656
http://svn.apache.org/r1614657
http://svn.apache.org/r1614659
> 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)
