Ilya, thanks for your effort.
ср, 11 нояб. 2020 г. в 14:28, Ilya Kasnacheev :
> Hello!
>
> The fix is now merged.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 3 нояб. 2020 г. в 22:51, Ivan Daschinsky :
>
> > There is not a big problem to fix it.
> >
> > 1. Blocked thread is detected by another
Hello!
The fix is now merged.
Regards,
--
Ilya Kasnacheev
вт, 3 нояб. 2020 г. в 22:51, Ivan Daschinsky :
> 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.
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,
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
