GitHub user drfits opened a pull request:
https://github.com/apache/sling/pull/180
Added ability to specify TTL for separate health check
Added ability to specify TTL for separate health check in case of expensive
computations.
If property "hc.ttl" specified within HC - it will be used as TTL for
result, otherwise default TTL value
Ex.: in my case "hc" validating repository about 3-5 minutes therefore I
couldn't specify TTL globally to not impact on other "hc" results. This check I
couldn't execute by scheduler due to CPU loading, also results for this check
results remain relevant for an hour.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/drfits/sling sling-result-ttl
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/180.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #180
----
commit 24fec55cb4ce3e32bd68255d9cd5788f9b2b539f
Author: Evgeniy Fitsner <([email protected])>
Date: 2016-10-10T20:59:44Z
Added ability to specify TTL for separate health check in case of expensive
computations.
If property "hc.ttl" specified within HC - it will be used as TTL for
result, otherwise default TTL value
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
