[
https://issues.apache.org/jira/browse/IGNITE-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672745#comment-16672745
]
Vladimir Ozerov commented on IGNITE-9928:
-----------------------------------------
[~gvvinblade] too dangerous for a last-minute fix for 2.7. Let's target next
release. If someone hit that problem during testing, there are two options:
1) Take nightly build
2) Plan immediate 2.8 (say, in December), when all* fault-tolerance problems
will be cleared
* all, that we know
> 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.8
>
>
> 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)
