[jira] [Updated] (IGNITE-6507) Commit can be lost in network split scenario

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

     [ https://issues.apache.org/jira/browse/IGNITE-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Goncharuk updated IGNITE-6507:
-------------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> Commit can be lost in network split scenario
> --------------------------------------------
>
>                 Key: IGNITE-6507
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6507
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 2.1
>            Reporter: Alexei Scherbakov
>            Assignee: Alexey Goncharuk
>            Priority: Critical
>              Labels: important
>             Fix For: 2.6
>
>
> Commit can be lost in network split scenario
> Reproducer:
> https://github.com/ascherbakoff/ignite/blob/ignite-6507/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/dht/IgniteCacheTopologySplitTxConsistencyTest.java
> If routing will be switched to second data center, new transactions will no see commited state.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)