Changes for page Grouping - Deploy Possibilities
Last modified by Danniar Firdausy on 2024/09/27 09:18
From version 39.1
edited by Erik Bakker
on 2024/03/25 09:55
on 2024/03/25 09:55
Change comment:
There is no comment for this version
To version 40.1
edited by Bouke Reitsma
on 2024/03/29 09:14
on 2024/03/29 09:14
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.BoukeReitsma - Content
-
... ... @@ -27,7 +27,7 @@ 27 27 28 28 == 4. Failover Deployment Step == 29 29 30 -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 in which we have single-node leaders. 30 +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 in which we have single-node leaders (See 4.1). 31 31 32 32 [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-disabled-failover.png]] 33 33 ... ... @@ -37,8 +37,16 @@ 37 37 38 38 === 4.1 Failover Status Explained === 39 39 40 -To get 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. 41 41 42 +=== 4.1.1 Leader Status === 43 + 44 +=== 4.1.1 Folower Status === 45 + 46 +=== 4.1.1 Disabled Status === 47 + 48 +=== 4.1.1 Leader (single node) Status === 49 + 42 42 == 5. Key takeaways == 43 43 44 44 * Grouping is beneficial when external systems go through maintenance or downtime.