Why does redis have 16384 slots?
#Redis cluster does not use consistent hashing, but introduces the concept of hash slots. The Redis cluster has 16384 hash slots. Each key is checked modulo 16384 after CRC16 verification to determine which slot to place. Each node in the cluster is responsible for a part of the hash slot. But why is the number of hash slots 16384 (2^14)? This question was raised on github, and the author also gave an answer. Let’s briefly analyze it.
Why is it 16384 (2^14)?
When the redis node sends the heartbeat packet, all slots need to be put into the heartbeat packet so that the node can know the current cluster information. 16384=16k. When sending the heartbeat packet, it is compressed using bitmap. 2k (2 * 8 (8 bit) * 1024(1k) = 2K
), which means that 16k slots are created using 2k space.
Although using the CRC16 algorithm can allocate up to 65535 (2^16-1) slots, 65535=65k, after compression it is 8k (8 * 8 (8 bit) * 1024(1k) = 8K
), that is to say, 8k heartbeat packets are required. The author believes that it is not worth it; and generally a redis cluster will not have more than 1,000 master nodes, so the 16k slot is a more appropriate choice. .
Author's original words:
1. Ordinary heartbeat packets carry the complete configuration of the node. This configuration can be replaced with the old configuration in an idempotent manner to update the old configuration. . This means that they contain the node's slot configuration in its raw form, a 16k slot configuration would use 2k of memory, but using a 65k slot would use 8k of memory.
2. At the same time, due to other design compromises, the Redis cluster cannot be expanded to more than 1,000 nodes.
Therefore, 16k is more appropriate to ensure that each main device has enough slots, up to 1000. The node configuration information of redis is transmitted through bitmap storage. There is a compression process before transmission. The compression ratio has a great relationship with the number of slots and the number of nodes (because when N is small the bitmap would have slots/N bits set that is a large percentage of bits set.) [Number of slots/number of nodes] The larger N is, the smaller the compression ratio is.
For more Redis-related technical articles, please visit the Redis Tutorial## column to learn!
The above is the detailed content of Why does redis have 16384 slots?. 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
