[
https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663920#comment-16663920
]
ASF GitHub Bot commented on IGNITE-10003:
-----------------------------------------
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/5084
IGNITE-10003 Changed checkpointReadLock timeout failure type.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite ignite-10003
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5084.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5084
----
commit 61b26e4004bf70d40e8aae55422c8e60e11761ac
Author: Andrey Kuznetsov <stkuzma@...>
Date: 2018-10-25T15:34:02Z
IGNITE-10003 Changed checkpointReadLock timeout failure type.
----
> 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)
