[jira] [Closed] (SLING-5195) HeartbeatHandler should check for topology changes independently of long-during session.saves

["Stefan Egli (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Egli closed SLING-5195.
------------------------------

> HeartbeatHandler should check for topology changes independently of long-during session.saves
> ---------------------------------------------------------------------------------------------
>
>                 Key: SLING-5195
>                 URL: https://issues.apache.org/jira/browse/SLING-5195
>             Project: Sling
>          Issue Type: Bug
>    Affects Versions: Discovery Impl 1.1.8
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: Discovery Impl 1.2.0
>
>
> When running discovery.impl in a DocumentNodeStore cluster that is under heavy load and thus produces large delays, the HeartbeatHandler can sometimes be blocked in session.save for non-trivial amounts of time - longer than the heartbeat timeout for example. This has the effect that both the {{lastHeartbeat}} property is no longer updated but also that the topology is not checked and updated towards the listeners. These two facts should be separated within the HeartbeatHandler though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)