summaryrefslogtreecommitdiff
path: root/etc
diff options
context:
space:
mode:
authorjiansong <jian.song@easystack.cn>2017-04-11 19:12:13 -0700
committerjian.song <jian.song@easystack.cn>2017-04-26 03:08:28 +0000
commitdbeff81d5049131f0b9b129ae7c42fcec2ff746d (patch)
treebde1eab4c0e3083f43a820f7ec8648bb3b575884 /etc
parente320489c5777b5f2bf78852e10b05b3980e5cb23 (diff)
downloadtrove-dbeff81d5049131f0b9b129ae7c42fcec2ff746d.tar.gz
Add port 16379 to conf.sample
This is a point that is easily hidden. In the case of not open port 16379, redis cluster can still be deployed successfully, but this success is a false success, there is no data communication between the various nodes. This is because 16379 is the port for data port[1]. We set the default value in cfg, but in the case of conf,it is easy to be covered. Adding 16379 to conf.sample helps the user to reduce some problem caused by the redis configuration. [1]:https://redis.io/topics/cluster-tutorial Change-Id: If517072c1c875df68106af14dac1802bb959d17e
Diffstat (limited to 'etc')
-rw-r--r--etc/trove/trove-taskmanager.conf.sample2
-rw-r--r--etc/trove/trove.conf.sample2
2 files changed, 2 insertions, 2 deletions
diff --git a/etc/trove/trove-taskmanager.conf.sample b/etc/trove/trove-taskmanager.conf.sample
index 03f619dc..e034a573 100644
--- a/etc/trove/trove-taskmanager.conf.sample
+++ b/etc/trove/trove-taskmanager.conf.sample
@@ -227,7 +227,7 @@ device_path = /dev/vdb
[redis]
# Format (single port or port range): A, B-C
# where C greater than B
-tcp_ports = 6379
+tcp_ports = 6379, 16379
# redis uses local storage
volume_support = False
# default device_path = None
diff --git a/etc/trove/trove.conf.sample b/etc/trove/trove.conf.sample
index 054d63bd..2440d96b 100644
--- a/etc/trove/trove.conf.sample
+++ b/etc/trove/trove.conf.sample
@@ -222,7 +222,7 @@ ignore_dbs = mysql, information_schema, performance_schema
[redis]
-tcp_ports = 6379
+tcp_ports = 6379, 16379
#redis uses local storage
volume_support = False
# default device_path = None