To disable some dangerous commands for Redis cluster, the method used is to add the following in the configuration file:
Rename-command Flushall Hufuflushall
Rename-command Flushdb Hufuflushdb
Rename-command Keys Hufukeys
This poses a problem, after rebooting outside the server, will cause the Redis service in cluster not to start, and will also be reported "Unknown command ' Flushall ' reading the Append only file". The usual practice of shutting down the persistent configuration "AppendOnly No" does not start the service. Then start the Redis instance service. However, when you connect to the Cluster service, you will be prompted to cluster unavailable when you encounter the following issues. At this point the role of REDIS-TRIB.RB is reflected in the implementation of the fix Operation Cluster service can be restored. However, the result of modifying the persistent configuration is that the Redis data cannot be returned because of a shutdown operation or an unexpected event. At this point, the redis-trib.rb add function for the problem of Redis instances to increase the slave, and then through the failover way to master and slave switch. The process is very tortuous, but who let Redis-cluster is still a semi-automatic Cluster service!
This article from "Good Life, happy work!" "Blog, be sure to keep this provenance http://yjw1983.blog.51cto.com/265702/1854600
Unknown command ' Flushall ' reading the Append only file