[jira] [Updated] (IGNITE-12956) Fully prepared TX rolled back on recovery if TX coordinator failed and some primary has only reads

["Anton Vinogradov (Jira)" <ji...@apache.org>]

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

Anton Vinogradov updated IGNITE-12956:
--------------------------------------
    Fix Version/s: 2.9

> Fully prepared TX rolled back on recovery if TX coordinator failed and some primary has only reads
> --------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-12956
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12956
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Anton Vinogradov
>            Assignee: Anton Vinogradov
>            Priority: Major
>             Fix For: 2.9
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We have 3 nodes with partitioned cache with 2 backups.
>  A - tx coordinator.
>  B and C - other nodes.
> Let's start tx from A and perform
> {noformat}
> cache.put(primaryKeyA, someVal);
> cache.get(primaryKeyB;
> tx.prepare();
> {noformat}
> then kill A.
> Expected: tx recovered and
> {noformat}
> cache.get(primaryKeyA)!=null
> {noformat}
> Actual: tx rolled back and
>  and
> {noformat}
> cache.get(primaryKeyA)==null
> {noformat}
> Reason: Node C has only 1 active transaction (because reads not propagated to backup), but expect to have 2.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)