Added an important point on failover (#438)
Honestly, active-passive stateful systems are terrible. Never have found one that worked, there's always too much data incongruency or other random errors. Stateless applications, like routers, are great. But not your Jenkins master. Co-authored-by: bowiz2 <bowiz1@gmail.com> Co-authored-by: Anandha Krishnan S <anandajith@gmail.com>pull/1079/head
parent
9a8838867d
commit
7c00e7eccc
|
@ -552,6 +552,7 @@ Active-active failover can also be referred to as master-master failover.
|
||||||
|
|
||||||
* Fail-over adds more hardware and additional complexity.
|
* Fail-over adds more hardware and additional complexity.
|
||||||
* There is a potential for loss of data if the active system fails before any newly written data can be replicated to the passive.
|
* There is a potential for loss of data if the active system fails before any newly written data can be replicated to the passive.
|
||||||
|
* A stateful system that does not have built-in support for Active-Passive failover will usually not work as expected if an external tool is used to facilitate failover.
|
||||||
|
|
||||||
### Replication
|
### Replication
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue