[IGNITE-9928] MVCC TX: Late affinity assignment support.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Component/s: mvcc
• Assignee: Igor Seliverstov
• Reporter: Roman Kondakov
• Created: 18/Oct/18 09:30
• Updated: 21/Nov/18 12:21
• Resolved: 21/Nov/18 12:18

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. 

Issue Links

• incorporates: IGNITE-9985 MVCC TX: fix backup mappings
• is related to: IGNITE-10264 MVCC: Enlist request failure on backup can cause grid hanging.
• is related to: IGNITE-8405 Sql query may see intermediate results of topology changes and perform mapping incorrectly
• is related to: IGNITE-9949 MVCC TX: Scan query can return wrong result on unstable topology
• links to: GitHub Pull Request #5057
• links to: TC run