From 7c00e7eccccf81bae6e2341c6d047f3adae829b6 Mon Sep 17 00:00:00 2001 From: Ido Ophir Date: Mon, 14 Apr 2025 08:42:10 +0300 Subject: [PATCH] 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 Co-authored-by: Anandha Krishnan S --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 5e5e771d..3c1a154e 100644 --- a/README.md +++ b/README.md @@ -552,6 +552,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