From 1d051210041c78a7afb8cfb54b6a050fe3be6045 Mon Sep 17 00:00:00 2001 From: Docker Library Bot Date: Mon, 3 Aug 2015 17:01:47 -0700 Subject: [PATCH] Run update.sh --- aerospike/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aerospike/README.md b/aerospike/README.md index 3bc9b75d3..0ac5d1721 100644 --- a/aerospike/README.md +++ b/aerospike/README.md @@ -66,7 +66,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