[
https://issues.apache.org/jira/browse/IGNITE-19234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-19234:
---------------------------------------
Description:
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.
was: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.
> 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)
