You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/10/18 16:39:00 UTC
[jira] [Commented] (IGNITE-9679) Document critical workers liveness
checking implementation
[ https://issues.apache.org/jira/browse/IGNITE-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655548#comment-16655548 ]
Andrey Kuznetsov commented on IGNITE-9679:
------------------------------------------
[~Artem Budnikov], this issue is not blocked anymore, your help with it is appreciated.
> Document critical workers liveness checking implementation
> ----------------------------------------------------------
>
> Key: IGNITE-9679
> URL: https://issues.apache.org/jira/browse/IGNITE-9679
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Andrey Kuznetsov
> Priority: Major
> Fix For: 2.7
>
>
> Newly implemented critical worker thread liveness checks should be mentioned in Ignite Documentation. Brief description of the functionality follows.
> Ignite node has a number of critical worker threads that should be alive and responsive, otherwise node's health is not guaranteed. These threads monitor each other periodically and track two aspects for a thread being checked:
> - whether it's alive;
> - whether it updates its internal heartbeat timestamp.
> Whenever at least one of the above conditions is violated, checker thread logs the error and calls currently configured {{FailureHandler}}.
> {{IgniteConfiguration.SystemWorkerBlockedTimeout}} configuration property affects monitoring behavior. At runtime monitoring settings can be changed via {{FailureHandlingMxBean}}.
> By default, liveness checks are enabled, but blocked system worker detection will not lead to failure handler invocation, see {{FailureProcessor#getDefaultFailureHandler}} .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)