[
https://issues.apache.org/jira/browse/SLING-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563989#comment-15563989
]
Georg Henzler commented on SLING-6126:
--------------------------------------
[~drfits] Would using hc.async.cronExpression (see
https://sling.apache.org/documentation/bundles/sling-health-check-tool.html#configuring-health-checks)
be an option? The problem of just extending the TTL is, that users calling the
long-running HC after a TTL has expired will not receive a result but a timeout
(only a reload after 3-5 minutes gives an adequate result then). Using an async
HC will never return a timeout (but always the last result).
> Ability to specify TTL for separate health check
> ------------------------------------------------
>
> Key: SLING-6126
> URL: https://issues.apache.org/jira/browse/SLING-6126
> Project: Sling
> Issue Type: Improvement
> Components: Health Check
> Reporter: Evgeniy Fitsner
>
> Currently there is no ability to specify TTL for separate health check.
> Ex.: in my case "hc" validating against repository about 3-5 minutes
> therefore I couldn't specify TTL globally to not impact on other "hc"
> results. This "hc" I couldn't execute by scheduler to prevent CPU from high
> loading, also results for this check remains relevant for an 1-3 hours.
> Therefore if it make sense not only for me I've added "[pull
> request|https://github.com/apache/sling/pull/180]"; for this functionality:
> * If property "hc.ttl" specified within HC - it will be used as TTL for
> result, otherwise cache will use default TTL value
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
