Skip to Content
Last modified by dfirdausy on 2024/09/27 09:18
From version 31.1
edited by BoukeReitsma
on 2024/03/08 14:54
Change comment: There is no comment for this version
To version 29.1
edited by BoukeReitsma
on 2024/03/08 12:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -25,14 +25,8 @@
25 25  
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.
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, and consequently, ...
29 29  
30 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-disabled-failover.png]]
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.
33 -
34 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-failover-deployment-step.png]]
35 -
36 36  == 5. Key takeaways ==
37 37  
38 38  * Grouping is beneficial when external systems go through maintenance or downtime.