[
https://issues.apache.org/jira/browse/IGNITE-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov updated IGNITE-9928:
-------------------------------------
Description: On unstable topology SQL queries are mapped to random
partitions in OWNED state (regardless whether it's going to be evicted or not)
but updates take into consideration current ideal affinity assignment only (in
other words updates are sent to current backups only and don't touch partitions
which are going to be evicted) what causes a situation when subsequent reads
may not see previous updates. (was: SQL query can return wrong results during
rebalancing. Reproducer:
{{CacheMvccPartitionedSqlCoordinatorFailoverTest#testPutAllGetAll_ClientServer_Backups1_Restart_Scan}})
> MVCC TX: Late affinity assignment support.
> ------------------------------------------
>
> Key: IGNITE-9928
> URL: https://issues.apache.org/jira/browse/IGNITE-9928
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Roman Kondakov
> Assignee: Igor Seliverstov
> Priority: Major
> Fix For: 2.7
>
>
> On unstable topology SQL queries are mapped to random partitions in OWNED
> state (regardless whether it's going to be evicted or not) but updates take
> into consideration current ideal affinity assignment only (in other words
> updates are sent to current backups only and don't touch partitions which are
> going to be evicted) what causes a situation when subsequent reads may not
> see previous updates.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
