[jira] [Commented] (IGNITE-1265) Remote cross-cache transactions are not committed during changing topology

["Alexey Goncharuk (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702277#comment-14702277 ] 

Alexey Goncharuk commented on IGNITE-1265:
------------------------------------------

There is no issue with {{commitIfLocked()}} because it possible that one-phase-commit {{prepareRequest}} is received by a node when a previous transaction for the same key is not committed yet. In this case {{commitIfLocked()}} will not proceed immediately, but will be called again from {{onOwnerChanged()}}. The transactions in {{COMMITTING}} state were hung because of the incorrect handling of invalid partitions.

> Remote cross-cache transactions are not committed during changing topology
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-1265
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1265
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.1.4
>            Reporter: Alexey Goncharuk
>            Assignee: Alexey Goncharuk
>
> Identified problems:
>  * invalidPartitions is not differentiated by cacheId, therefore when invalid partitions response is received, mapping can be mistakenly removed from transaction, but remote transaction still exists on remote node.
>  * commitIfLocked fails to verify owning entry (need to investigate)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)