[IGNITE-13564] Improve SYSTEM_WORKER_BLOCKED reporting.

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.9, 2.8.1
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Ivan Daschinsky
• Created: 09/Oct/20 08:54
• Updated: 04/May/21 16:22

Description

Currently, reporting of system thread blocking has major drawbacks.

1. As system worker blocking is detected by another thread, due to implementation, failure handler receives not full information about problem. In FailureContext we have only two fields – type and err. Throwable err is generated in thread-detector flow, so we lost a context of main problem.
2. Currently, due to implementation, we print not full stacktrace of blocking thread in org.apache.ignite.internal.worker.WorkersRegistry#onIdle.

This two drawbacks can lead to completely loss of information about blocking system thread.

I suggests:
1. Add another parameter in FailureContext, namely worker
2. Fix threaddump printing.

Issue Links

• incorporates: IGNITE-13575 Invalid blocking section in GridNioWorker and GridNioClientWorker leads to false positive blocking thread detection
• is related to: IGNITE-13665 Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
• links to: GitHub Pull Request #8345