Skip to Content
Last modified by Danniar Firdausy on 2024/09/27 09:18
From version 34.1
edited by Bouke Reitsma
on 2024/03/15 09:42
Change comment: There is no comment for this version
To version 40.1
edited by Bouke Reitsma
on 2024/03/29 09:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,16 +23,30 @@
23 23  
24 24  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-group-deployment-step.png]]
25 25  
26 +{{info}}Note that when you activate the stop action in a failover setup (on the leader container), it will activate the failover behaviour on the follower container{{/info}}
27 +
26 26  == 4. Failover Deployment Step ==
27 27  
28 -The configuration of a failover deployment step is similar as for the Group deployment step. The only difference is the action you can activate. The stop group actions make the inbounds of the currently selected container stop. If this group is the leader of the failover group. It will deactivate this group and start orignal follower group. However, it disables failover. Therefore, from this point were are running in a dubble setup in which we have single node leaders.
30 +The configuration for a failover deployment step is the same as for the group deployment step. The only difference is the action you can activate. The stop group action stops the inbounds of the selected container. It will also disable the failover, so if a follower is configured, it will **not** take over. Instead, from this point, we are running in a standard multi-container setup in which we have single-node leaders (See 4.1).
29 29  
30 30  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-disabled-failover.png]]
31 31  
32 -The start group step with failover will activate the current container as the leader of the failover setup. Therefore, resembling group names on other containers will become the followers. If these flows were running, they will be stopped.
34 +The start group step with failover will activate the current container as the leader of the failover setup. Therefore, group names resembling those on other containers will become the followers. If these flows were running, they will be stopped.
33 33  
34 34  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-failover-deployment-step.png]]
35 35  
38 +=== 4.1 Failover Status Explained ===
39 +
40 +Within a failover setup, the inbounds can have mulitple states depended on the configured or executed behaviour within the deployment plan. This section explains briefly the meaning on each of the states.
41 +
42 +=== 4.1.1 Leader Status ===
43 +
44 +=== 4.1.1 Folower Status ===
45 +
46 +=== 4.1.1 Disabled Status ===
47 +
48 +=== 4.1.1 Leader (single node) Status ===
49 +
36 36  == 5. Key takeaways ==
37 37  
38 38  * Grouping is beneficial when external systems go through maintenance or downtime.