From 8e4b0ea3bf596ee1fcaa72710a78f3c2b192b7ce Mon Sep 17 00:00:00 2001 From: bowiz2 Date: Thu, 21 May 2020 08:52:00 +0300 Subject: [PATCH] Added an important point on failover 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. --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 293b8ac5..142c4566 100644 --- a/README.md +++ b/README.md @@ -518,6 +518,7 @@ Active-active failover can also be referred to as master-master failover. * 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. +* 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