From ab55af7ae21c26a1b58b600ad2b6336d414dca62 Mon Sep 17 00:00:00 2001
From: Ronnie Sahlberg <sahlberg@ronnie>
Date: Tue, 5 Jun 2007 18:40:43 +1000
Subject: [PATCH] add some text about CTDB and in which scenarios it would be a
 good candidate to solve the users needs for a HA solution

(This used to be ctdb commit 77d58ba6fc6fa34678aa0201311139201d4679c8)
---
 ctdb/web/ctdb.html | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/ctdb/web/ctdb.html b/ctdb/web/ctdb.html
index b89e32df45d..26b85a9d7c0 100644
--- a/ctdb/web/ctdb.html
+++ b/ctdb/web/ctdb.html
@@ -81,6 +81,17 @@ databases are consistent. Recovery typically takes between 1 and 3
 seconds. During the recovery period the databases are 'frozen', and
 all IO operations by ctdb clients are suspended.
 
+<h3>Is CTDB a HA solution?</h3>
+Yes and no.<br>
+CTDB is primarily developed around the concept of having a shared cluster 
+filesystem shared across all the nodes in the cluster to provide the features
+required for building a NAS cluster.<br>
+Thus CTDB relies on an external component (the cluster filesystem) to provide 
+the mechanisms for avoiding split-brain and other difficult tasks.<br><br>
+However, If you applications do need a clustered filesystem for all the nodes, 
+in that scenario CTDB will provide a very easy to install and manage 
+solution for your clustering HA needs.
+
 <h3>IP Takeover</h3>
 
 When a node in a cluster fails, CTDB will arrange that a different
-- 
2.47.3