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

Summary

Details

Page properties
Content
... ... @@ -52,7 +52,7 @@
52 52  
53 53  When you are done, then you can save your changes, and proceed with creating a new release. For this, you will need to create a new release from your "Create phase", to include all configurations that eMagiz has provided in your now failover-enabled Create phase. Once you have done this, give the release a name and save it, then you can proceed with activating the release and deploy it.
54 54  
55 -== 3.5 Trigger Failover ==
55 +== 3.5 Runtime Failover Status ==
56 56  
57 57  Once you have successfully deployed and run your release with the failover connector runtimes, then you can observe the follower and leadership status of your failover connector runtimes in your Deploy>Architecture. There, if you right-click your external machines (which have the failover connector runtimes) and select [["Start/Stop flows">>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-start-stop-flows.WebHome||target="blank"]], under the "Groups" tab, you will find the "Group name", "Failover status", as well as the "State" the connector runtime is in at that moment (whether it is now On or Off). See the screenshot below as an example.
58 58  
... ... @@ -60,6 +60,27 @@
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 +
64 +=== 3.2.1 Failover Status Explained ===
65 +
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 +
68 +==== 3.2.1.1 Leader Status ====
69 +
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 +
72 +==== 3.2.1.2 Follower Status ====
73 +
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 +
76 +==== 3.2.1.3 Disabled Status ====
77 +
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 +
80 +==== 3.2.1.4 Leader (single node) Status ====
81 +
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 +
63 63  == 4. Key takeaways ==
64 64  
65 65  * 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.