Or, How to Run Multiple Instances of Redis on One Machine. Why would you even want to do something like this? Well Redis is a single threaded application. So if you have a server with 8 cores and it runs Redis, only 1 of those cores will ever be used by Redis. By running multiple instances on the same machine and pinning each instance to specific CPU core you can better utilize the Cores to more quickly serve data....
So far we have covered a bit of ground in learning how to configure both Redis Sentinel and Redis Cluster for production. Now that we have an understanding of the server, and a running setup, its time to start digging into using Redis. It would be rather tedious and redundant to start going through all the various Redis Data types and regurgitating what is already in the documentation. Instead, its time to start writing some code....
Part I was an introduction to some basic knowledge needed to run Redis in production. Part II talked about Sentinel and Cluster a bit, then dove into standing up Sentinel for production. Part III we finished up Sentinel and tested it out Part IV we blew all that away and stood up Cluster. And now we’re going to pause for a minute on talking strictly Redis, and reflect on a few things you should do to run any of this in production....
In Part III we finished setting up Redis Sentinel and performed a test by shutting down the Primary and watching as Sentinel failed over to one of the Secondaries. In this article we are going to throw all of that away and start fresh, only this time we will deploy Redis Cluster to our 3 nodes. If you are following along with the Vagrant setup described in Part II then now is the time to run vagrant destroy....
In part 2 we looked at the 2 different ways Redis is setup in production, Cluster and Sentinel, and we started working towards configuring a Redis Sentinel Setup. We’re going to continue with Configuring Redis Sentinel using our already running Redis1, Reds2, and Redis3 machines. The next step in the process is to setup the Redis-Sentinel services in Docker. We are going to Pin our services to specific nodes to ensure we don’t ever schedule multiple Redis-Sentinel instances on the same node....