From bacc362cff08cc61ea76e36d314ea778679513cb Mon Sep 17 00:00:00 2001 From: Lucien Volmar Date: Sun, 2 Aug 2015 03:47:01 -0700 Subject: [PATCH] Mesh Clustering --- aerospike/content.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aerospike/content.md b/aerospike/content.md index 0756ae440..51595d57c 100644 --- a/aerospike/content.md +++ b/aerospike/content.md @@ -60,7 +60,7 @@ A full example: ## Clustering -Aerospike recommends using multicast clustering whenever possible, however, we are currently working to figure out how to best support multicast via Docker. For the time being, it will be best to setup Mesh Clustering. We are open to pull-requests with proposals on how to implement multicast for our Dockerfile. +Aerospike recommends using Mesh Clustering. Mesh uses TCP point to point connections for heartbeats. Each node in the cluster maintains a heartbeat connection to all other nodes. Please see [http://www.aerospike.com/docs/operations/configure/network/heartbeat/#mesh-unicast-heartbeat](http://www.aerospike.com/docs/operations/configure/network/heartbeat/#mesh-unicast-heartbeat) ### Mesh Clustering