Skip to Content
Last modified by Danniar Firdausy on 2024/09/27 09:18
From version 38.1
edited by Bouke Reitsma
on 2024/03/22 13:52
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
... ... @@ -27,14 +27,26 @@
27 27  
28 28  == 4. Failover Deployment Step ==
29 29  
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 makes the inbounds of the selected container stop. On top of that, it will disable the failover, so if there is a follower configured it will **not** take over. Instead, from this point were are running in a standard multi container 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).
31 31  
32 32  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-disabled-failover.png]]
33 33  
34 -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.
35 35  
36 36  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-failover-deployment-step.png]]
37 37  
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 +
38 38  == 5. Key takeaways ==
39 39  
40 40  * Grouping is beneficial when external systems go through maintenance or downtime.