Skip to Content
Last modified by Danniar Firdausy on 2024/09/27 09:18
From version 35.1
edited by Bouke Reitsma
on 2024/03/15 09:43
Change comment: There is no comment for this version
To version 37.1
edited by Bouke Reitsma
on 2024/03/22 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,9 +23,11 @@
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 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 dubble setup in which we have single node leaders.
29 29  
30 30  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-disabled-failover.png]]
31 31