ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-10972) MERGE INTO hangs in MVCC mode with unsorted keys
Date Thu, 14 Feb 2019 15:31:00 GMT

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

Vladimir Ozerov updated IGNITE-10972:
-------------------------------------
    Component/s:     (was: sql)

> MERGE INTO hangs in MVCC mode with unsorted keys
> ------------------------------------------------
>
>                 Key: IGNITE-10972
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10972
>             Project: Ignite
>          Issue Type: Task
>          Components: mvcc
>    Affects Versions: 2.7
>            Reporter: Ilya Kasnacheev
>            Priority: Major
>         Attachments: CacheMvccMergeConflictTest.java
>
>
> right now, if you perform repeatedly
> MERGE INTO T(K, V) VALUES(k1, v1), (k2, v2), (k3, v3);
> and in parallel
> MERGE INTO T(K, V) VALUES(k2, v2), (k1, v1);
> you will eventually see a deadlock. This is expected behavior as per old putAll behavior,
but the expectation is that you should see "Cannot serialize transaction" errors instead of
deadlock when using MVCC.
> When doing MERGE INTO with sorted keys you will not get deadlock but will see a lot of
"Cannot serialize transaction" exception with expectation that such statements to not conflict
instead since they are ordered.
> Please see attached test and userlist discussion.



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

Mime
View raw message