ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9928) MVCC TX: Late affinity assignment support.
Date Wed, 21 Nov 2018 12:22:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694645#comment-16694645
] 

ASF GitHub Bot commented on IGNITE-9928:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/5057


> 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)

Mime
View raw message