You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Georg Henzler (JIRA)" <ji...@apache.org> on 2016/10/18 11:46:00 UTC
[jira] [Comment Edited] (SLING-6126) Ability to specify TTL for
separate health check
[ https://issues.apache.org/jira/browse/SLING-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15585247#comment-15585247 ]
Georg Henzler edited comment on SLING-6126 at 10/18/16 11:45 AM:
-----------------------------------------------------------------
Updated documentation in [r1765416|http://svn.apache.org/r1765416]
was (Author: henzlerg):
Updated documentation in [r1765377|http://svn.apache.org/r1765416]
> 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)