What is the solution to redis avalanche and penetration
The solution is: 1. Cache penetration, you can also cache empty data and use Bloom filters; 2. Cache avalanche, you can set the corresponding hotspot key to never expire, combine multiple caches, and purchase Third-party Redis and staggered expiration time, the expiration time can be randomly generated.
The operating environment of this tutorial: Windows 7 system, Redis version 5.0.10, DELL G3 computer.
Redis cache penetration and solutions
1. Cache penetration
1. When the key queried by the user does not exist in redis, the corresponding id does not exist in the database. If it is attacked by illegal users, a large number of requests will be hit directly on the db, causing downtime and affecting the entire system. This phenomenon is called cache penetration.
2. Solution 1: Cache empty data, such as empty strings, empty objects, empty arrays or lists, the code is as follows
if (list != null && list.size() > 0) { redisOperator.set("subCat:" + rootCatId, JsonUtils.objectToJson(list)); } else { redisOperator.set("subCat:" + rootCatId, JsonUtils.objectToJson(list), 5*60); }
3. Solution 2: Bloom Filter
Bloom filter: Determine whether an element is in an array, as shown in the figure below. It uses binary to store and occupies a relatively small memory. 0 represents non-existence and 1 represents existence, which increases query efficiency. Soon, when a value is saved, an algorithm will be used to save the corresponding value to a certain position on the Bloom filter set. There may be multiple keys at a certain position. When a non-existent key value is passed in, , matches the set, and if it does not match, it will return a null
Disadvantages: 1. 1% misjudgment rate, when a key does not exist in the Bloom array, but due to this misjudgment rate, Under certain circumstances, it is judged that the key exists. The longer the array, the lower the false positive rate, and the shorter the array, the higher the false positive rate.
2. When we want to delete a certain key value, it is The content in our database and redis will be deleted, but it cannot be deleted in the Bloom array, because there will be a key at a certain position in the array. If we want to delete it, we will change 1 to 0, but all the keys in it will be changed. All values are deleted
3. The code complexity will also increase because we have to maintain an additional collection. When we use redis cluster, Bloom filter must be used in combination with redis
2. Redis cache avalanche
1. Cache avalanche: The data in the cache fails in large batches, and then this use requires a large number of requests to come in, but because all the keys in redis If it fails, all requests will be sent to the db, causing downtime
2. Solution
Set the corresponding hotspot key to never expire
The expiration time is staggered, the expiration time is randomly generated, and the expiration time of hotspot data is set longer, and the expiration time of non-hotspot data can be set shorter.
Multiple cache combinations, for example: To request entry, you can request redis now. When redis does not exist, request memcache. If it does not exist, request db
Purchase third-party Redis (Alibaba Cloud or Tencent Cloud) redis)
Related tutorial recommendations: Redis tutorial
The above is the detailed content of What is the solution to redis avalanche and penetration. 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.

Using the Redis directive requires the following steps: Open the Redis client. Enter the command (verb key value). Provides the required parameters (varies from instruction to instruction). Press Enter to execute the command. Redis returns a response indicating the result of the operation (usually OK or -ERR).

Using Redis to lock operations requires obtaining the lock through the SETNX command, and then using the EXPIRE command to set the expiration time. The specific steps are: (1) Use the SETNX command to try to set a key-value pair; (2) Use the EXPIRE command to set the expiration time for the lock; (3) Use the DEL command to delete the lock when the lock is no longer needed.

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.

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.
