Configure some of the pits that Redis cluster encounters under Windows

When I was not busy recently, I decided to learn about Redis. Because it's always working under Windows, no Linux, no way to choose to configure Redis under Windows.

There are many articles on configuring Redis clusters under Windows, such as: http://www.cnblogs.com/linjisong/p/6081312.html, I'm here to talk about some of the pits I've encountered.

1. Configuration files

After the Redis service is installed, there will be two configuration files, such as:

According to the official explanation, one is the command prompt to start Redis use, one is dedicated to the service, but I have a machine, changed the server's configuration file, does not work, the port changes. Later, two files were changed to OK.

2. The profile option must not have spaces in front of it

Because some configurations are annotated (that is, there is a # in front of the configuration item), I delete the # and leave a space, as a result, the following error occurred in starting Redis:

View Log display errors are:

Syslog-ident = Redis
Invalid argument during Startup:unknown conf file Parameter:cluster-config-file

I thought it was redis. The Windows Service version does not support this configuration option, a variety of online search and check, the last to know that the original Redis configuration items can not be preceded by spaces. I'm really drunk.

3. Not all16384 slots is covered by nodes error

This error was encountered when creating a Redis cluster with the REDIS-TRIB.RB create command: Not all16384 slots is covered by nodes.

This article: Http://www.cnblogs.com/xling/p/5253063.html said is the slot is not assigned, need to perform cluster meet, but after I have executed, the problem remains as usual .

Finally read this article: http://blog.csdn.net/vtopqx/article/details/50235891 use the REDIS-TRIB.RB fix command to solve the problem.

Configure some of the pits that Redis cluster encounters under Windows