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 42.1
edited by Erik Bakker
on 2024/03/29 13:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.BoukeReitsma
1 +XWiki.ebakker
Content
... ... @@ -37,11 +37,11 @@
37 37  
38 38  === 4.1 Failover Status Explained ===
39 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.
40 +Within a failover setup, each inbound can have one of the below listed distinct states. This section explains briefly the meaning on each of the states.
41 41  
42 42  === 4.1.1 Leader Status ===
43 43  
44 -If the leader status is shown, all the inbounds with the same group name in this container are actively running.
44 +If the leader status is shown, it means that this container is the leader for this group. As a result, all inbound components with the same group name in this container are actively running.
45 45  
46 46  === 4.1.2 Follower Status ===
47 47  
... ... @@ -49,11 +49,11 @@
49 49  
50 50  === 4.1.3 Disabled Status ===
51 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.
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 please use the aforementioned steps in Deploy -> Architecture.
53 53  
54 54  === 4.1.4 Leader (single node) Status ===
55 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.
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 or with the port configuration.
57 57  
58 58  == 5. Key takeaways ==
59 59