Add Warning About HA Deployment Across Multiple Datacenters (#7707)

* Add Warning About HA Deployment Across Multiple Datacenters * Update source/scale/high-availability-cluster-based-deployment.rst --------- Co-authored-by: Carrie Warner (Mattermost) <[email protected]>
mattermost · Jan 20, 2025 · 633d214 · 633d214
1 parent d6e7156
commit 633d214
Showing 1 changed file with 5 additions and 1 deletion.
diff --git a/source/scale/high-availability-cluster-based-deployment.rst b/source/scale/high-availability-cluster-based-deployment.rst
@@ -25,6 +25,10 @@ Update sequence for continuous operation
 
   **Exception:** Changes to configuration settings that require a server restart, and server version upgrades that involve a change to the database schema, require a short period of downtime. Downtime for a server restart is around five seconds. For a database schema update, downtime can be up to 30 seconds.
 
+.. important::
+
+   Mattermost does not support high availability deployments spanning multiple datacenters. All nodes in a high availability cluster must reside within the same datacenter to ensure proper functionality and performance.
+
 Deployment guide
 ----------------
 
@@ -592,4 +596,4 @@ Modify configuration settings directly through ``config.json`` :ref:`following t
 Messages do not post until after reloading
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-When running in high availability mode, make sure all Mattermost application servers are running the same version of Mattermost. If they are running different versions, it can lead to a state where the lower version app server cannot handle a request and the request will not be sent until the frontend application is refreshed and sent to a server with a valid Mattermost version. Symptoms to look for include requests failing seemingly at random or a single application server having a drastic rise in goroutines and API errors.
+When running in high availability mode, make sure all Mattermost application servers are running the same version of Mattermost. If they are running different versions, it can lead to a state where the lower version app server cannot handle a request and the request will not be sent until the frontend application is refreshed and sent to a server with a valid Mattermost version. Symptoms to look for include requests failing seemingly at random or a single application server having a drastic rise in goroutines and API errors.