Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 29.2
edited by Danniar Firdausy
on 2024/09/27 09:37
Change comment: There is no comment for this version
To version 28.115
edited by Danniar Firdausy
on 2024/09/27 09:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Failover - Deploy Possibilities
1 +Setting up Failover - Deploy Phase
Content
... ... @@ -2,7 +2,7 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  
5 -In the previous microlearning, we discussed what needs to be done in the Design and Create phase to enable failover for systems that are configured to have them in the Design phase. Next to that, we also discussed that setting up this failover functionality in your model requires you to execute some steps in your Design, Create, and lastly Deploy phase. Picking up from what we have toggled in the Create phase, in this microlearning, we will focus on the steps and configurations that you have to make in the Deploy phase to activate the active/passive failover functionality.
5 +In the previous microlearning, we discussed what needs to be done in the Create phase to enable failover for systems that are configured to have them in the Design phase. Next to that, we also discussed that setting up this failover functionality in your model requires you to execute some steps in your Design, Create, and lastly Deploy phase. Picking up from what we have toggled in the Create phase, in this microlearning, we will focus on the steps and configurations that you have to make in the Deploy phase to activate the active/passive failover functionality.
6 6  
7 7  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
8 8  
... ... @@ -60,26 +60,6 @@
60 60  
61 61  The example above shows that, in that moment, the first runtime instance is currently active and acting as the Leader, while the second runtime instance that acts as the Follower is Off. You can also manually switch the leadership from one to another by clicking the Play or Stop button on the right-side.
62 62  
63 -=== 3.5.1 Failover Status Explained ===
64 -
65 -Within a failover setup, each inbound can have one of the distinct states listed below. This section explains briefly the meaning of each state.
66 -
67 -==== 3.5.1.1 Leader Status ====
68 -
69 -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.
70 -
71 -==== 3.5.1.2 Follower Status ====
72 -
73 -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).
74 -
75 -==== 3.5.1.3 Disabled Status ====
76 -
77 -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.
78 -
79 -==== 3.5.1.4 Leader (single node) Status ====
80 -
81 -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.
82 -
83 83  == 4. Key takeaways ==
84 84  
85 85  * By enabling multiple runtimes across different machines, you can configure groups to operate in active/passive failover mode, ensuring continued operation during connection failures, system maintenances, or outages.