[ https://issues.apache.org/jira/browse/IGNITE-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686258#comment-16686258 ]
Artem Budnikov commented on IGNITE-9679: ---------------------------------------- [~pgarg] I updated the description because the implementation has changed. By default, the failure handler is not called when a critical worker stops responding. If the user wants to call the failure handler in such situations, additional configuring is required, that's why I added another configuration example in the "Critical Workers Health Check" section. Please review. > 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 > Assignee: Artem Budnikov > 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)