There is not a big problem to fix it.

1. Blocked thread is detected by another worker. Currently we take dump
before printing it to log with zero depth. This can be easily fixed.

2. We should propagate BlockedThreadExceptiob to failureCtx with original
stacktrace of blocked thread. StackFrames, obtained in previous step, can
be used to construct stacktrace of BlockedThreadException.


вт, 3 нояб. 2020 г., 19:15 Ilya Kasnacheev <ilya.kasnach...@gmail.com>:

> Hello!
>
> https://issues.apache.org/jira/browse/IGNITE-13665
>
> The notorious problem with failure handler's thread dump, which nobody has
> bothered to investigate, until now.
> "IgnitionEx$IgniteNamedInstance$2.apply"
>
> If anybody knows how to fix it, please suggest.
>
> Regards,
> --
> Ilya Kasnacheev
>

Reply via email to