[
https://issues.apache.org/jira/browse/IGNITE-8920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556009#comment-16556009
]
ASF GitHub Bot commented on IGNITE-8920:
----------------------------------------
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4432
IGNITE-8920 Fix transaction hanging on exception during commit
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8920
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4432.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 #4432
----
commit 751bc07779821220a066c9c11479169b86476cf2
Author: Pavel Kovalenko <jokserfn@...>
Date: 2018-07-25T16:23:22Z
IGNITE-8920 WIP
commit 7c6169e12513a8df00a38b6d39b61991e754e42e
Author: Pavel Kovalenko <jokserfn@...>
Date: 2018-07-25T17:24:44Z
IGNITE-8920 WIP
----
> Node should be failed when during tx finish indices are corrupted.
> ------------------------------------------------------------------
>
> Key: IGNITE-8920
> URL: https://issues.apache.org/jira/browse/IGNITE-8920
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Ivan Daschinskiy
> Assignee: Pavel Kovalenko
> Priority: Major
> Fix For: 2.7
>
>
> While transaction is processed after receiving finish request
> (IgniteTxHandler.finish) , node should be failed by FailureHandler if page
> content of indices is corrupted. Currently this case is not handled properly
> and cause to long running transactions over the grid.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)