Skip to Content
Last modified by Danniar Firdausy on 2024/09/27 09:18
From version 47.2
edited by Danniar Firdausy
on 2024/09/27 09:16
Change comment: There is no comment for this version
To version 46.10
edited by Danniar Firdausy
on 2024/09/13 10:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Grouping - Deploy Possibilities
1 +Deploy Possibilities
Content
... ... @@ -26,10 +26,40 @@
26 26  
27 27  {{info}}Note that when you activate the stop action in a failover setup (on the leader container), it will trigger the failover behavior on the follower container{{/info}}
28 28  
29 +=== 3.2. Failover Deployment Step ===
30 +
31 +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 with single-node leaders (See 3.2.1).
32 +
33 +[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-disabled-failover.png]]
34 +
35 +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 would be stopped.
36 +
37 +[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-failover-deployment-step.png]]
38 +
39 +=== 3.2.1 Failover Status Explained ===
40 +
41 +Within a failover setup, each inbound can have one of the distinct states listed below. This section explains briefly the meaning of each state.
42 +
43 +==== 3.2.1.1 Leader Status ====
44 +
45 +If the leader status is shown, it means that this container is the Leader of this group. As a result, all inbound components with the same group name in this container are actively running.
46 +
47 +==== 3.2.1.2 Follower Status ====
48 +
49 +The follower status is closely tied to the leader status. Inbounds with this status act as the backup. When the active Leader stops, the followers will take the Leader status. By default, the starting status of these inbounds is stopped (grey lightbulb).
50 +
51 +==== 3.2.1.3 Disabled Status ====
52 +
53 +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 if the Leader stops working. To continue failover behavior, please use the steps above in Deploy -> Architecture.
54 +
55 +==== 3.2.1.4 Leader (single node) Status ====
56 +
57 +The last possible status is Leader (single node). This means the inbound acts as a separate normal inbound with no (failover) connectivity to other containers with a similar configured group name. Suppose this status occurs in a failover setup. In that case, there is a problem in the inbounds' configuration, most likely in the cache manager or port configuration.
58 +
29 29  == 4. Key takeaways ==
30 30  
31 31  * Grouping is beneficial when external systems go through maintenance or downtime.
32 -* 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 +* 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
33 33  * The role naming in both grouping and failover is crucial. The group name needs to match **exactly** to make it work.
34 34  * You can control group and failover steps from the deployment plan.
35 35  * Container inbounds can have a different failover status.