[
https://issues.apache.org/jira/browse/IGNITE-10104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780306#comment-16780306
]
Igor Seliverstov edited comment on IGNITE-10104 at 2/28/19 10:11 AM:
---------------------------------------------------------------------
[~rkondakov], one comment from me, we shouldn't split SFU query into two parse
results. We need to have all query info in one place. Another point is that
inTx flag of {{QueryParserCacheKey}} is a part of hash. Since at this point
(before parsing) we don't know whether it's SFU or not we will duplicate even
regular selects into two parse results depending on whether we in tx or not.
Please rework it. Everything else is OK.
was (Author: gvvinblade):
[~rkondakov], one comment from me, we shouldn't split SFU query into two parse
results. We need to have all query info in one place. Please rework it.
Everything else is OK.
> 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)
