Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.116
edited by Danniar Firdausy
on 2024/09/27 09:18
Change comment: There is no comment for this version
To version 29.7
edited by Danniar Firdausy
on 2024/09/27 09:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Setting up Failover - Deploy Phase
1 +Failover - Deploy Possibilities
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 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 Design and Create phase to enable failover for systems connecting with your model. 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  
... ... @@ -14,16 +14,14 @@
14 14  
15 15  This microlearning describes what configuration that you will have to do in the Deploy phase, based on what you have configured in the Design and Create phase, to enable failover for systems connecting with your model. The grouping and failover functionality is relevant when faced with maintenance and outages of systems connected to your model. The failover functionality assists in that case and allows you to have a fallback option on an active connection.
16 16  
17 -== 3. Deploy Phase Configuration ==
17 +== 3. Deploy Phase Possibilities ==
18 18  
19 19  == 3.1 Deploy Architecture ==
20 20  
21 -After finishing up your configuration in the Create phase, you can then move to your Deploy>Architecture. Here, you will see the new router containers, which we have seen in the Design>Architecture, to be added to your external machines. When you press "Start Editing" in this page, and then press "Apply to environment", you will be faced with a pop-up page that informs you that these router containers will be created for this specific environment as shown in the screenshot below.
21 +After finishing up your configuration in the Create phase, you can then move to your Deploy>Architecture. Here, you will see the new router containers, which we have seen in the Design>Architecture, to be added to your external machines. When you press "Start Editing" in this page, and then press "Apply to environment", you will be faced with a pop-up page that informs you that these router containers will be created for this specific environment.
22 22  
23 -{{info}}**Note**: what you see below is a typical situation where you already have two external machines deployed. Please refer to these microlearnings if you want to know more about [[deploying on-premise machine(s)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-start-stop-flows.WebHome||target="blank"]] and [[apply to environment>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-understanding-deploy-architecture-basic||target="blank"]].{{/info}}
23 +{{info}}**Note**: Here, we assume a typical situation where you have already two external machines deployed. Please refer to these microlearnings if you want to know more about [[deploying on-premise machine(s)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-start-stop-flows.WebHome||target="blank"]] and [[apply to environment>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-understanding-deploy-architecture-basic||target="blank"]].{{/info}}
24 24  
25 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-router-containers.png]]
26 -
27 27  == 3.2 Failover Balancing Preference ==
28 28  
29 29  Once you have applied the changes, when you go to the "Details" of each of those machines via right-clicking them, then you can find and set for each failover runtime the preferred machine to be the leader. As an example shown in the screenshot below, there are two runtimes that are enabled for failover and you can select whether that runtime running in that "External 01" machine is the preferred leader. Another option is to set the runtime that you select as the backup, or reset it back to "None" if you want. Next to that, notice that here you can find the "Internal IP address" and "Failover port" fields, which have been pre-filled in with property placeholders. We will comeback to these properties later in the following sections.
... ... @@ -60,24 +60,23 @@
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  
61 +=== 3.5.1 Failover Status Explained ===
63 63  
64 -=== 3.2.1 Failover Status Explained ===
65 -
66 66  Within a failover setup, each inbound can have one of the distinct states listed below. This section explains briefly the meaning of each state.
67 67  
68 -==== 3.2.1.1 Leader Status ====
65 +==== 3.5.1.1 Leader Status ====
69 69  
70 70  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.
71 71  
72 -==== 3.2.1.2 Follower Status ====
69 +==== 3.5.1.2 Follower Status ====
73 73  
74 74  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).
75 75  
76 -==== 3.2.1.3 Disabled Status ====
73 +==== 3.5.1.3 Disabled Status ====
77 77  
78 78  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.
79 79  
80 -==== 3.2.1.4 Leader (single node) Status ====
77 +==== 3.5.1.4 Leader (single node) Status ====
81 81  
82 82  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.
83 83