You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Ilya Kasnacheev <il...@gmail.com> on 2020/11/03 16:15:18 UTC
Incorrect failure handler exceptions
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
Re: Incorrect failure handler exceptions
Posted by Ivan Daschinsky <iv...@gmail.com>.
Ilya, thanks for your effort.
ср, 11 нояб. 2020 г. в 14:28, Ilya Kasnacheev <il...@gmail.com>:
> Hello!
>
> The fix is now merged.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 3 нояб. 2020 г. в 22:51, Ivan Daschinsky <iv...@gmail.com>:
>
> > 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 <il...@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
> > >
> >
>
--
Sincerely yours, Ivan Daschinskiy
Re: Incorrect failure handler exceptions
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
The fix is now merged.
Regards,
--
Ilya Kasnacheev
вт, 3 нояб. 2020 г. в 22:51, Ivan Daschinsky <iv...@gmail.com>:
> 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 <il...@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
> >
>
Re: Incorrect failure handler exceptions
Posted by Ivan Daschinsky <iv...@gmail.com>.
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 <il...@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
>