From 3d939266be28d4db5359fea0ce7e9aa7666a8a84 Mon Sep 17 00:00:00 2001 From: Dara Kong Date: Tue, 29 Jul 2014 10:49:56 -0700 Subject: sentinel: Decouple bind address from address sent to other sentinels There are instances such as EC2 where the bind address is private (behind a NAT) and cannot be accessible from WAN. https://groups.google.com/d/msg/redis-db/PVVvjO4nMd0/P3oWC036v3cJ --- sentinel.conf | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'sentinel.conf') diff --git a/sentinel.conf b/sentinel.conf index 2384e9bc7..be18888c0 100644 --- a/sentinel.conf +++ b/sentinel.conf @@ -4,6 +4,13 @@ # The port that this sentinel instance will run on port 26379 +# announce +# The IP that other sentinels use to connect to this sentinel instance +# +# Example: +# +# sentinel announce 1.2.3.4 + # dir # Every long running process should have a well-defined working directory. # For Redis Sentinel to chdir to /tmp at startup is the simplest thing -- cgit v1.2.1