You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/03 09:59:02 UTC
[jira] [Updated] (IGNITE-9949) MVCC TX: Scan query can return wrong
result on unstable topology
[ https://issues.apache.org/jira/browse/IGNITE-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-9949:
------------------------------------
Fix Version/s: (was: 2.8)
2.9
> MVCC TX: Scan query can return wrong result on unstable topology
> ----------------------------------------------------------------
>
> Key: IGNITE-9949
> URL: https://issues.apache.org/jira/browse/IGNITE-9949
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Roman Kondakov
> Priority: Major
> Labels: mvcc_stability, transactions
> Fix For: 2.9
>
>
> Scan query map nodes do not take into account topology version when filtering primary partitions. See method {{GridCacheQueryManager#scanIterator}} - each node takes it's current topology version. This causes wrong partition filtering results.
> To fix this problem the single topology version should be taken on reduce node propagated to map nodes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)