Summary of redis3.0 installation errors

1. After all master nodes are configured, "ERR Invalid node address specified" is reported

   Since redis-trib.rb does not support domain names or host names well, the ip:port method should be used when creating a cluster

   redis-trib.rb create ip1:port1 ip2:port2 ip3:port3

    

2. When a cluster is created, an err slot 0 is already busy (redis::commanderror)

   This is because the cluster creation between them was unsuccessful, and all files in nodes.conf and dir need to be deleted (be careful not to delete redis.conf)

    

3. Always in "Waiting for the cluster to join................................." when creating a cluster condition

   The reason for this problem is unknown, but the solution is to change the bind 127.0.0.1 local loopback port to a physical interface in the redis.conf file.

    

4. No response for a long time when installing ruby ​​redis

   This is due to the Tianchao network, the solution is to change the ruby ​​source (please baidu yourself) or install it manually

5. moguang@ubsvr13:/opt/redis-unstable/src$ ./redis-trib.rb create 192.168.1.13:6379 192.168.1.15:6380 192.168.1.40:6381    Creating cluster
   Connecting to node 192.168.1.13:6379: OK
   Connecting to node 192.168.1.15:6380: OK
   Connecting to node 192.168.1.40:6381: OK
   Performing hash slots allocation on 3 nodes…
   Using 3 masters:
   192.168.1.40:6381
   192.168.1.15:6380
   192.168.1.13:6379
   M: 225b7f54c67483f71955db78312a90c67941fff0 192.168.1.13:6379
   slots:10922-16383 (5462 slots) master
   M: bca62c53e7f50d7c83dd418ed23e08fb8a4e9bb5 192.168.1.15:6380
   slots:5461-10921 (5461 slots) master
   M: 47483c65a705025aab28ee74da210a2dce41bc41 192.168.1.40:6381
   slots:0-5460 (5461 slots) master
   Can I set the above configuration? (type ‘yes’ to accept): yes
   /usr/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:97:in call': ERR Slot 16011 is already busy (Redis::CommandError)
   from /usr/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:2432:inmethod_missing’
   from /usr/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:37:in synchronize'
   from /usr/lib/ruby/1.8/monitor.rb:242:inmon_synchronize’
   from /usr/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:37:in synchronize'
   from /usr/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:2431:inmethod_missing’
   from ./redis-trib.rb:203:in flush_node_config'
   from ./redis-trib.rb:571:inflush_nodes_config’
   from ./redis-trib.rb:570:in each'
   from ./redis-trib.rb:570:inflush_nodes_config'
   from ./redis-trib.rb:820:in create_cluster_cmd'
   from ./redis-trib.rb: 1026:insend'
   from ./redis-trib.rb:1026
   After checking, this is due to the configuration information left when the cluster configuration failed last time. Just delete the file where the cluster-config-file defined in redis.conf is located, restart redis-server and run redis-trib.