[
https://issues.apache.org/jira/browse/UNOMI-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Sinovassin-Naïk updated UNOMI-924:
-------------------------------------------
Fix Version/s: unomi-3.1.0
> Impossible to call healthcheck concurrently
> -------------------------------------------
>
> Key: UNOMI-924
> URL: https://issues.apache.org/jira/browse/UNOMI-924
> Project: Apache Unomi
> Issue Type: Bug
> Reporter: Jerome Blanchard
> Priority: Major
> Fix For: unomi-4.0.0, unomi-3.1.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> To avoid heavy load for healthcheck, a lock has been placed to raise an
> exception when a healthcheck is already running.
> This strategy seems good at the beginning but in production we are facing
> concurrent calls to healthcheck from multiple HA Proxy nodes. As the lock
> generated an HTTP error 500, HAProxy mark the unomi node as failing.
> The goal is to fix that behavior by allowing concurrent calls but having only
> one thread calculating healthcheck and a caching strategy.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
