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

Summary

Details

Page properties
Content
... ... @@ -23,45 +23,22 @@
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 -
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 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).
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.
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, group names resembling those on other containers will become the followers. If these flows were running, they will be stopped.
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.
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 -If the leader status is shown, all the inbounds with the same group name in this container are actively running.
45 -
46 -=== 4.1.2 Follower Status ===
47 -
48 -The follower status is closely tied to the leader status. Inbounds with this status act as the backup if the active leaders stops. In that situation, the followers will take the Leader status. By default, the starting status of these inbounds is stopped (grey lightbulb).
49 -
50 -=== 4.1.3 Disabled Status ===
51 -
52 -If the container inbounds have the status disabled the failover is inactive. This means that the components are stopped (grey lightbulb) but will not react in case the leader stops working. To continue failover behaviour it should be manually be activated via Deploy -> Architecture.
53 -
54 -=== 4.1.4 Leader (single node) Status ===
55 -
56 -The last possible status is the Leader (single node). This means that the inbound acts as a separate normal inbound with no (failover) connectivity to other containers with a similar configured group name. If this status occurs in a failover setup, there is a problem in the configuration of the inbounds, most likely in the configuration of the cache manager.
57 -
58 58  == 5. Key takeaways ==
59 59  
60 60  * Grouping is beneficial when external systems go through maintenance or downtime.
61 61  * Failover can have the additional benefit of having a fallback scenario while still adhering to the requirement that there can only be one active connection at a time
62 62  * The role naming in both grouping and failover is crucial. The group name needs to match **exactly** to make it work.
63 -* You can control group and failover steps from the deployment plan.
64 -* Container inbounds can have a different failover status.
41 +* You can control group and failover steps from the deployment plan
65 65  
66 66  == 6. Suggested Additional Readings ==
67 67