Add section about coordinator deployment in HA (#1221)

* Add section about coordinator deployment

* Improve wording

* Pairwise deployment

Author: as51340

pages/clustering/high-availability.mdx

@@ -40,6 +40,7 @@ specifying only `--management-port` flag. This port is used for RPC network comm
 instances. When started by default, the data instance is MAIN. The coordinator will ensure that no data inconsistency can happen during and after the instance's
 restart. Once all instances are started, the user can start adding data instances to the cluster.
 
+
 <Callout type="info">
 
 The Raft consensus algorithm ensures that all nodes in a distributed system
@@ -51,6 +52,15 @@ since Raft, as a consensus algorithm, works by forming a majority in the decisio
 
 </Callout>
 
+<Callout type="info">
+
+When deploying coordinators to servers, you can use the instance of almost any size. Instances of 4GiB or 8GiB will suffice since coordinators'
+job mainly involves network communication and storing Raft metadata. Coordinators and data instances can be deployed on same servers (pairwise)
+but from the availability perspective, it is better to separate them physically.
+
+</Callout>
+
+
 
 ## Bolt+routing
 
@@ -874,4 +884,4 @@ that and automatically promote the first alive REPLICA to become the new MAIN. T
 
 </Steps>
 
-<CommunityLinks/>
+<CommunityLinks/>