You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Pligin (Jira)" <ji...@apache.org> on 2025/08/13 11:40:00 UTC

[jira] [Created] (IGNITE-26197) Add configuration information into the message about critical thread being blocked

Vladimir Pligin created IGNITE-26197:
----------------------------------------

             Summary: Add configuration information into the message about critical thread being blocked
                 Key: IGNITE-26197
                 URL: https://issues.apache.org/jira/browse/IGNITE-26197
             Project: Ignite
          Issue Type: Task
          Components: failure handler ai3
            Reporter: Vladimir Pligin


When critical threads are being blocked there is a message in the ignite log:

{{}}
{code:java}
2025-08-13 05:11:22:488 +0000 [WARNING][%poc-tester-SERVER-172.25.4.33-id-0%common-scheduler-0][FailureManager] Possible failure suppressed according to a configured handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=SYSTEM_WORKER_BLOCKED] org.apache.ignite.internal.failure.StackTraceCapturingException: IGN-CMN-65535 A critical thread is blocked for 1041 ms that is more than the allowed 500 ms, it is "poc-tester-SERVER-172.25.4.33-id-0-network-worker-55" prio=10 Id=126 RUNNABLE (in native){code}
{{Information about the part of config, responsible for the timeout (what kind of timeout was hit exactly), should be added to the message}}
{code:java}
configuration.maxAllowedLagMillis(){code}
It will help users tune their systems easier.{{{}{}}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)