infinite Waiting for the cluster to join...............................................

[cherry4477]

HI, i tried to run a redis cluster in openshift which bases on k8s following the steps describes in this repo, but there is a problem of infinite Waiting for the cluster to join..... when the redis.rb was executed.

the six pods are running correctly. and here is the log of redis.rb:

>>> Creating cluster
>>> Performing hash slots allocation on 6 nodes...
Using 3 masters:
172.30.122.99:6379
172.30.122.98:6379
172.30.122.97:6379
Adding replica 172.30.122.96:6379 to 172.30.122.99:6379
Adding replica 172.30.122.95:6379 to 172.30.122.98:6379
Adding replica 172.30.122.94:6379 to 172.30.122.97:6379
M: 7e42913aabc8f55dd412a959da9b0bd58a4133c9 172.30.122.99:6379
   slots:0-5460 (5461 slots) master
M: c2e738fa25345b98ca14d3d8a240980c7ffbda1b 172.30.122.98:6379
   slots:5461-10922 (5462 slots) master
M: 81078cb5c548c036277e70781901e027186c01d6 172.30.122.97:6379
   slots:10923-16383 (5461 slots) master
S: faed0f1ce212fc1e25434ca278b082c52d3668be 172.30.122.96:6379
   replicates 7e42913aabc8f55dd412a959da9b0bd58a4133c9
S: 47147b7aef64511d7fbd33be11593eee0f852c29 172.30.122.95:6379
   replicates c2e738fa25345b98ca14d3d8a240980c7ffbda1b
S: 2c95e9e47cfc0697acaf3f0c233788f11a4f17bd 172.30.122.94:6379
   replicates 81078cb5c548c036277e70781901e027186c01d6
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
Waiting for the cluster to join......................................................................................................................................

and here is the logs of the six pods:
pod1:

Server started, Redis version 3.2.0
1:M 19 Jul 06:56:32.611 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 19 Jul 06:56:32.611 * The server is now ready to accept connections on port 6379
1:M 19 Jul 06:56:55.376 # configEpoch set to 1 via CLUSTER SET-CONFIG-EPOCH
1:M 19 Jul 06:56:55.400 # IP address for this node updated to 10.1.19.36

pod2:

1:M 19 Jul 06:56:29.264 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 19 Jul 06:56:29.264 # Server started, Redis version 3.2.0
1:M 19 Jul 06:56:29.265 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 19 Jul 06:56:29.265 * The server is now ready to accept connections on port 6379
1:M 19 Jul 06:56:57.672 # configEpoch set to 2 via CLUSTER SET-CONFIG-EPOCH

pod3:

1:M 19 Jul 06:56:22.636 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 19 Jul 06:56:22.636 # Server started, Redis version 3.2.0
1:M 19 Jul 06:56:22.636 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 19 Jul 06:56:22.636 * The server is now ready to accept connections on port 6379
1:M 19 Jul 06:56:51.286 # configEpoch set to 3 via CLUSTER SET-CONFIG-EPOCH

pod 4 pod 5 and pod6 are the same as pod 3, the only difference is "configEpoch set to 4,5,6 via CLUSTER SET-CONFIG-EPOCH"

anyone could help~~~~~

[Aabed]

@cherry4477 any luck with that?

[cherry4477]

i'm afraid no.....

孟静 （Meng Jing) LDP云平台部

北京亚信智慧数据科技有限公司
地址：北京市海淀区中关村软件园二期亚信研发中心大厦
电话：[phone]
手机：[phone]
邮件：[e-mail]
网站：www.asiainfodata.com

From: Aabed
Date: 2016-10-17 21:47
To: kelseyhightower/kubernetes-redis-cluster
CC: cherry4477; Mention
Subject: Re: [kelseyhightower/kubernetes-redis-cluster] infinite Waiting for the cluster to join............................................... (#1)
@cherry4477 any luck with that?
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[ricl]

the same ;-(

[JackXu]

Did you solve this problem? @cherry4477 @riclava

[Rafael Galdêncio]

For anyone trying to solve this issue, you have to add cluster-announce-ip in args section of each ReplicaSet:
command: ["redis-server"]
args:
- /conf/redis.conf
- --cluster-announce-ip
- "10.99.1.1" # SERVICE CLUSTER IP HERE