[
https://issues.apache.org/jira/browse/FELIX-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746320#comment-16746320
]
Georg Henzler commented on FELIX-6018:
--------------------------------------
Obviously activating this filter comes at a cost for every request (unless
autoDisableFilter is configured to true), however the cost is reasonably small
- tests showed it takes around 0.2 ms per call. (~200,000 ns, see
http://svn.apache.org/viewvc/felix/trunk/healthcheck/core/src/main/java/org/apache/felix/hc/core/impl/filter/ServiceUnavailableFilter.java?view=markup&pathrev=1850907#l196
on how to track this).
> Servlet Filter to answer arbitrary http requests with 503 if certain HC tags
> are in non-OK status
> -------------------------------------------------------------------------------------------------
>
> Key: FELIX-6018
> URL: https://issues.apache.org/jira/browse/FELIX-6018
> Project: Felix
> Issue Type: New Feature
> Components: Health Checks
> Reporter: Georg Henzler
> Assignee: Georg Henzler
> Priority: Major
>
> Servlet Filter to answer arbitrary http requests with 503 if certain HC tags
> are in non-OK result:
> * Can be used together with ongoing deployment filter FELIX-6017 to answer
> all http requests with 503 during deployment
> * Can replace sling startup filter SLING-2347 for sling platforms
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
