ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-6507) Commit can be lost in network split scenario
Date Wed, 01 Nov 2017 11:48:01 GMT

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

Alexey Goncharuk reassigned IGNITE-6507:
----------------------------------------

    Assignee: Alexey Goncharuk

> 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.4
>
>
> 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
(v6.4.14#64029)

Mime
View raw message