Example analysis of redis cluster principle
Principle of redis cluster
If you rely on sentinels to achieve high availability of redis, and if you want to support high concurrency while accommodating massive amounts of data, you need a redis cluster. Redis cluster is a distributed data storage solution provided by redis. The cluster shares data through data sharding and provides replication and failover functions.
Node
A redis cluster consists of multiple nodes, and multiple nodes are connected through the cluster meet command. The handshake process of the nodes:
Node A receives the cluster meet command from the client
A sends a meet message to B based on the received IP address and port number
Node B receives the meet message and returns pong
A knows that B has received the meet message, returns a ping message, and the handshake is successful
Finally, node A will spread the information of node B to other nodes in the cluster through the gossip protocol, and other nodes will also shake hands with B
slot
redis saves data in the form of cluster sharding. The entire cluster database is divided into 16384 slots. Each node in the cluster can handle 0-16384 slots. When all 16384 slots in the database are processed by nodes, the cluster is in Online status, otherwise as long as one slot is not processed, the offline status will be processed. Slots can be assigned to corresponding nodes for processing through the cluster addslots command.
slot is a bit array, the length of the array is 16384/8=2048, and each bit of the array is represented by 1 to be processed by the node, and 0 represents not processed. As shown in the figure, it means that node A processes 0 -7 slot.
When the client sends a command to the node, if it happens to find that the slot belongs to the current node, the node will execute the command. Otherwise, a MOVED command will be returned to the client to guide the client to the correct node. (The MOVED process is automatic)
If you add or remove nodes, it is also very convenient to reallocate slots. Redis provides tools to help realize slot migration. The entire process is completely online and does not need to stop the service. .
Failover
If node A sends a ping message to node B, and node B does not respond to pong within the specified time, then node A will mark node B as pfail suspected offline state, and at the same time Send the status of B to other nodes in the form of messages. If more than half of the nodes mark B as pfail status, B will be marked as fail offline. At this time, failover will occur, and priority will be given to replicating data from Multiple slave nodes choose one to become the master node and take over the slot of the offline node. The whole process is very similar to that of the sentinel, both of which are based on the Raft protocol for election.
The above is the detailed content of Example analysis of redis cluster principle. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











Redis cluster mode deploys Redis instances to multiple servers through sharding, improving scalability and availability. The construction steps are as follows: Create odd Redis instances with different ports; Create 3 sentinel instances, monitor Redis instances and failover; configure sentinel configuration files, add monitoring Redis instance information and failover settings; configure Redis instance configuration files, enable cluster mode and specify the cluster information file path; create nodes.conf file, containing information of each Redis instance; start the cluster, execute the create command to create a cluster and specify the number of replicas; log in to the cluster to execute the CLUSTER INFO command to verify the cluster status; make

How to clear Redis data: Use the FLUSHALL command to clear all key values. Use the FLUSHDB command to clear the key value of the currently selected database. Use SELECT to switch databases, and then use FLUSHDB to clear multiple databases. Use the DEL command to delete a specific key. Use the redis-cli tool to clear the data.

To read a queue from Redis, you need to get the queue name, read the elements using the LPOP command, and process the empty queue. The specific steps are as follows: Get the queue name: name it with the prefix of "queue:" such as "queue:my-queue". Use the LPOP command: Eject the element from the head of the queue and return its value, such as LPOP queue:my-queue. Processing empty queues: If the queue is empty, LPOP returns nil, and you can check whether the queue exists before reading the element.

On CentOS systems, you can limit the execution time of Lua scripts by modifying Redis configuration files or using Redis commands to prevent malicious scripts from consuming too much resources. Method 1: Modify the Redis configuration file and locate the Redis configuration file: The Redis configuration file is usually located in /etc/redis/redis.conf. Edit configuration file: Open the configuration file using a text editor (such as vi or nano): sudovi/etc/redis/redis.conf Set the Lua script execution time limit: Add or modify the following lines in the configuration file to set the maximum execution time of the Lua script (unit: milliseconds)

Use the Redis command line tool (redis-cli) to manage and operate Redis through the following steps: Connect to the server, specify the address and port. Send commands to the server using the command name and parameters. Use the HELP command to view help information for a specific command. Use the QUIT command to exit the command line tool.

Redis counter is a mechanism that uses Redis key-value pair storage to implement counting operations, including the following steps: creating counter keys, increasing counts, decreasing counts, resetting counts, and obtaining counts. The advantages of Redis counters include fast speed, high concurrency, durability and simplicity and ease of use. It can be used in scenarios such as user access counting, real-time metric tracking, game scores and rankings, and order processing counting.

There are two types of Redis data expiration strategies: periodic deletion: periodic scan to delete the expired key, which can be set through expired-time-cap-remove-count and expired-time-cap-remove-delay parameters. Lazy Deletion: Check for deletion expired keys only when keys are read or written. They can be set through lazyfree-lazy-eviction, lazyfree-lazy-expire, lazyfree-lazy-user-del parameters.

In Debian systems, readdir system calls are used to read directory contents. If its performance is not good, try the following optimization strategy: Simplify the number of directory files: Split large directories into multiple small directories as much as possible, reducing the number of items processed per readdir call. Enable directory content caching: build a cache mechanism, update the cache regularly or when directory content changes, and reduce frequent calls to readdir. Memory caches (such as Memcached or Redis) or local caches (such as files or databases) can be considered. Adopt efficient data structure: If you implement directory traversal by yourself, select more efficient data structures (such as hash tables instead of linear search) to store and access directory information
