Details
Description
When failure handler catches an issue in striped pool, maybe in some other cases, thread dump is as folows:
[2020-10-10T10:10:10,100][WARN ][grid-timeout-worker-#22%cluster%][] Possible failure suppressed accordingly to a configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker [name=sys-stripe-0, igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]]] org.apache.ignite.IgniteException: GridWorker [name=sys-stripe-0, igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890] at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1859) [ignite-core.jar] at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1854) [ignite-core.jar] at org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233) [ignite-core.jar] at org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:296) [ignite-core.jar] at org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:265) [ignite-core.jar] at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) [ignite-core.jar] at java.lang.Thread.run(Thread.java:834) [?:?]
when the actual stack trace from the relevant thread is hidden somewhere deep below. And may even be suppressed. This is a usability nightmare.
Attachments
Issue Links
- relates to
-
IGNITE-13564 Improve SYSTEM_WORKER_BLOCKED reporting.
- Open
- links to