[jira] (IGNITE-18171) Descibe nodes start/stop scenarios

["Andrey Mashenkov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-18171 ]


    Andrey Mashenkov deleted comment on IGNITE-18171:
    -------------------------------------------

was (Author: amashenkov):
Startup scenarios:
 # CMG -> MSG -> DNG
 # CMG -> DNG -> MSG
 # MSG -> CMG -> DNG  
 # MSG -> DNG -> CMG
 # DNG -> CMG -> MSG
 # DNG -> MSG -> CMG

NB: Groups may be disjoint or subset of other group or intersects. These are different cases to be checked.

 

Stop scenarios are the same, let check service level degrades in expected way.

NB: Stop quorum will be enough to achieve group unavailability. Stop order (leader or follower) doesn't matter, as it is covered by other tests.

> Descibe nodes start/stop scenarios
> ----------------------------------
>
>                 Key: IGNITE-18171
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18171
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Andrey Mashenkov
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>
> h2. Definitions.
> We can distinguish next cluster node groups, see below. Each node may be part of one or more groups.
>  * Cluster Management Group (CMG), that control new nodes join process.
>  * MetaStorage group (MSG), that hosts meta storage.
>  * Data node group (DNG), that just hosts tables partitions.
> The components (CMG, meta storage, tables components) are depends on each other, but may resides on different (even disjoint) node subsets. So, some components may become temporary unavailable, and dependant components must be aware of such issues and handle them (wait, retry, throw exception or whatever) in expected way, which has to be documented also.
> [See IEP for details|https://cwiki.apache.org/confluence/display/IGNITE/IEP-77%3A+Node+Join+Protocol+and+Initialization+for+Ignite+3]
> h2. Motivation.
> As of now, the correct way to start the grid (after it was stopped) is: start CMG nodes, then Meta Storage nodes, then Data nodes. And in backward order for correct stop. Other scenarios are not tested and may lead to unexpected behaviour.
> Let's describe all possible scenarios, expected behaviour for each of them and extend test coverage.



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