You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Kondakov (JIRA)" <ji...@apache.org> on 2019/03/05 15:33:00 UTC

[jira] [Comment Edited] (IGNITE-10104) MVCC TX: client SFU doesn't work on replicated caches

    [ https://issues.apache.org/jira/browse/IGNITE-10104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782014#comment-16782014 ] 

Roman Kondakov edited comment on IGNITE-10104 at 3/5/19 3:32 PM:
-----------------------------------------------------------------

[~gvvinblade], [~vozerov], [~amashenkov], patch is ready for review. TC looks good.


was (Author: rkondakov):
[~gvvinblade], patch is ready for review. TC looks good.

> MVCC TX: client SFU doesn't work on replicated caches
> -----------------------------------------------------
>
>                 Key: IGNITE-10104
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10104
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc, sql
>            Reporter: Igor Seliverstov
>            Assignee: Roman Kondakov
>            Priority: Major
>              Labels: mvcc_stabilization_stage_1, transactions
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When select for update executes from client node the execution is sent to random owning node. On that node dht enlist operation is started what causes an assertion error because dht enlist operation implies that the node is primary for all processed keys.
> see {{CacheMvccReplicatedBackupsTest.testBackupsCoherenceWithLargeOperations}} 



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