[
https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725903#comment-16725903
]
Andrey Gura commented on IGNITE-10003:
--------------------------------------
[~andrey-kuznetsov][~Jokser][~agoncharuk][~ivan.glukos]
Guys, I've thought that {{SYSTEM_WORKER_BLOCKED}} isn't valid failure type for
this case. First of all we can get into this situations from any thread. What
about adding new failure type {{SYSTEM_CRITICAL_OPERATION_FAILED}} that will
describe situations like this? If it is ok, we should add this new failure type
to {{AbstractFailureHandler.ignoredFailureTypes}} and use this failure type in
cases of checkpoint read lock acquisition was timed out. One mote thing that
should be done is providing proper error explanation in exception message. May
be we should also introduce system critical operations/error codes. But it
topic for separate discussion.
Thoughts?
> Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read
> lock timeout detected
> ------------------------------------------------------------------------------------------------
>
> Key: IGNITE-10003
> URL: https://issues.apache.org/jira/browse/IGNITE-10003
> Project: Ignite
> Issue Type: Task
> Affects Versions: 2.7
> Reporter: Andrey Kuznetsov
> Assignee: Andrey Kuznetsov
> Priority: Trivial
> Fix For: 2.8
>
>
> {{GridCacheDatabaseSharedManager#failCheckpointReadLock}} should report
> {{SYSTEM_WORKER_BLOCKED}} to failure handler: it is closer to the truth and
> default consequenses are not so severe as opposed to {{CRITICAL_ERROR}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
