You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/05/29 15:11:00 UTC

[jira] [Commented] (IGNITE-19234) Race between additional volatile storage assignment update and installation of RAFT snapshot

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

Roman Puchkovskiy commented on IGNITE-19234:
--------------------------------------------

This is only about in-memory storages (namely, in-memory pagemem), it does not harm persistent storages.

> Race between additional volatile storage assignment update and installation of RAFT snapshot
> --------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-19234
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19234
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> Code in TableManager#updateAssignmentInternal() has a specific case for volatile storages, see IGNITE-16668. For them, an additional rebalance might be triggered. This additional rebalance causes data races with IncomingSnapshotCopier.
> This is only about in-memory storages (namely, in-memory pagemem), it does not harm persistent storages.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)