You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (Jira)" <ji...@apache.org> on 2021/03/31 15:42:00 UTC
[jira] [Updated] (IGNITE-13873) Milti-cell transaction changes may
be not visible (during some time) after the Cellular switch
[ https://issues.apache.org/jira/browse/IGNITE-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anton Vinogradov updated IGNITE-13873:
--------------------------------------
Fix Version/s: (was: 2.10.1)
> Milti-cell transaction changes may be not visible (during some time) after the Cellular switch
> ----------------------------------------------------------------------------------------------
>
> Key: IGNITE-13873
> URL: https://issues.apache.org/jira/browse/IGNITE-13873
> Project: Ignite
> Issue Type: Improvement
> Reporter: Anton Vinogradov
> Assignee: Anton Vinogradov
> Priority: Critical
> Labels: iep-45
> Fix For: 2.11
>
> Attachments: master (as 2.9) vs improved (as dev) .png
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Transactions over some cells may be recovered after the stale data read.
> For example:
> We have 2 cells, the first contains partitions for k1, second for k2.
> Tx with put(k1,v1) and put(k2,v2) started and prepared.
> Then node from the first cell, which is the primary for k1, failed.
> Currently, the second cell (with key2) may finish the cellular switch before tx recovered and stale data read is possible.
> Primaries from the {{tx.transactionNodes()}} should be taken into account instead of the current logic that awaits for all transactions located on nodes who are backups to the failed primary.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)