[
https://issues.apache.org/jira/browse/IGNITE-14873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17530510#comment-17530510
]
Kirill Gusakov commented on IGNITE-14873:
-----------------------------------------
[~sanpwc] suggested two more good cases to cover here
https://github.com/apache/ignite-3/pull/759 :
- Let's add a test, within separate ticket, that will check that everything
works fine, if node files after tblConfiguration.change but before ms.invoke. I
expect that it should work properly, but nevertheless the test will be useful.
- Let's also add a test within separate ticket that will check that partially
applied rebalance-invokes because of wrapped nodeStoppingException in the
middle will abort ms notification flow and properly recovered on
nodeRestart/leaderRe-election. I mean success invokes for ssome k paritions and
RuntimeException(NodeStoppingExpcetion) on k + 1.
> Failover scenarios
> ------------------
>
> Key: IGNITE-14873
> URL: https://issues.apache.org/jira/browse/IGNITE-14873
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> Need to implement a comprehensive set of tests in order to cover data
> rebalancing.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
