[
https://issues.apache.org/jira/browse/IGNITE-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752244#comment-16752244
]
Roman Kondakov commented on IGNITE-9265:
----------------------------------------
I think we should consider possible reordering of
{{GridDhtTxQueryEnlistRequest}} when updating backups after this ticket is
implemented. With this reordering updates may be applied in different order on
primary and on backup and this can lead to data inconsistency between primary
and backup nodes.
> MVCC TX: Two rows with the same key in one MERGE statement produce an
> exception
> -------------------------------------------------------------------------------
>
> Key: IGNITE-9265
> URL: https://issues.apache.org/jira/browse/IGNITE-9265
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Igor Seliverstov
> Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> In case the operation like {{MERGE INTO INTEGER (_key, _val) KEY(_key) VALUES
> (1,1),(1,2)}} is called an exception is occurred.
> Correct behavior: each next update on the same key overwrites pervious one
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
