[ 
https://issues.apache.org/jira/browse/SLING-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Georg Henzler resolved SLING-6126.
----------------------------------
    Resolution: Fixed

> 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
>            Assignee: Georg Henzler
>             Fix For: Health Check Core 1.2.6
>
>
> 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)

Reply via email to