sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-6126) Ability to specify TTL for separate health check
Date Mon, 27 Nov 2017 19:39:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267337#comment-16267337
] 

ASF GitHub Bot commented on SLING-6126:
---------------------------------------

Github user drfits closed the pull request at:

    https://github.com/apache/sling/pull/180


> 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.4.14#64029)

Mime
View raw message