[
https://issues.apache.org/jira/browse/IGNITE-18694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Uttsel updated IGNITE-18694:
-----------------------------------
Description:
h3. *Motivation*
DistributionZoneRebalanceEngine#dataNodesListener processes events with zones'
data nodes updates and invokes RebalanceUtil#updatePendingAssignmentsKeys with
new data nodes value. updatePendingAssignmentsKeys does async
metaStorageMgr#invoke. It's possible that dataNodesListener processed data
nodes event then the nodes crashed without updating assignments in metastorage.
h3. *Definition of Done*
Need to create a recovery for this case or make a guarantee that if the event
is processed, then the assignments were written to the metastorage.
> Recovery for DistributionZoneRebalanceEngine#metaStorageManager on
> DistributionZoneManager#start()
> --------------------------------------------------------------------------------------------------
>
> Key: IGNITE-18694
> URL: https://issues.apache.org/jira/browse/IGNITE-18694
> Project: Ignite
> Issue Type: Improvement
> Reporter: Sergey Uttsel
> Priority: Major
> Labels: ignite-3
>
> h3. *Motivation*
> DistributionZoneRebalanceEngine#dataNodesListener processes events with
> zones' data nodes updates and invokes
> RebalanceUtil#updatePendingAssignmentsKeys with new data nodes value.
> updatePendingAssignmentsKeys does async metaStorageMgr#invoke. It's possible
> that dataNodesListener processed data nodes event then the nodes crashed
> without updating assignments in metastorage.
> h3. *Definition of Done*
> Need to create a recovery for this case or make a guarantee that if the event
> is processed, then the assignments were written to the metastorage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
