[
https://issues.apache.org/jira/browse/IGNITE-18865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706267#comment-17706267
]
Roman Puchkovskiy commented on IGNITE-18865:
--------------------------------------------
The patch looks good to me
> Add a test for recovery after a full rebalance aborted with part of storages
> ----------------------------------------------------------------------------
>
> Key: IGNITE-18865
> URL: https://issues.apache.org/jira/browse/IGNITE-18865
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> There are two storages: MV storage and TX state storage.
> Suppose a full rebalancing for one of the storages ended successfully, and it
> has updated (not equal to -1) *lastAppliedIndex* and *lastAppliedTerm*, while
> for the other we did not have time to complete the full rebalancing and the
> node fell.
> What will happen to both storages after the node is powered on?
> I expect both stores to be cleared and have initial (equal to 0)
> *lastAppliedIndex* and *lastAppliedTerm*.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
