ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-5073) Race between partition exchange process and client cache operations
Date Tue, 23 May 2017 06:49:04 GMT

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

Semen Boikov updated IGNITE-5073:
---------------------------------
    Fix Version/s:     (was: 2.1)
                   2.2

> Race between partition exchange process and client cache operations
> -------------------------------------------------------------------
>
>                 Key: IGNITE-5073
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5073
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Semen Boikov
>            Assignee: Semen Boikov
>            Priority: Critical
>             Fix For: 2.2
>
>
> Added test reproducing issue IgniteCacheClientMultiNodeUpdateTopologyLockTest:
> - 3 servers (node1, node2, node3), 1 client
> - client starts pessimistic tx
> - client locks key1 on node2
> - new node joins, exchanges starts, on node3 there are no ongoging cache operations and
node3 sends GridDhtPartitionsSingleMessage to coordinator
> - client locks key2 on node3
> - client commits tx, when tx started on node2 finishes then node2 will send GridDhtPartitionsSingleMessage
to coordinator and exchange will be completed before tx on node3 finished
> One potential fix for this issue is change exchange protocol to use two steps.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message