redis key expiration settings
EXPIRE key seconds
is used to set an expiration time for a key. The second parameter indicates how many seconds will pass before the key expires. After a key expires, the key will be automatically deleted. In Redis terminology, keys with expiration times are often called volatile.
When using delete or overwrite operations on this key, the expiration time will be cleared. These operations include DEL, SET, GETSET and all *STORE commands. Those commands that modify the key value will not modify the expiration time, such as IINCR to modify the value, LPUSH to add a new value to the queue, and HSET to modify the members in the hash table.
If you just want to clear the expiration time, you can call the PERSIST command so that the key will not expire. The expiration time is an attribute of the key and will not change due to the key name modification (RENAME). When RENAME is used to overwrite other keys, only an overwriting effect has passed, and the renamed key will still retain its expiration time.
Note: calling the EXPIRE/PEXPIRE command with a non-positive number on a key, or calling EXPIREAT/PEXPIREAT with a past time will directly remove the key.
Update expiration time
Calling EXPIRE on a key with an expiration time can update the expiration time of the key.
Return value
Calling EXPIRE key seconds will return 0 or 1. 0 means that the key does not exist, and 1 means that the key has been set to timeout.
How Redis handles keys with expiration time
Keys with expiration time
Under normal circumstances, redis The key exists until the key is explicitly deleted (via the DEL command) or cleared due to memory constraints. Setting a timeout for a key requires additional memory to record relevant information. Redis will ensure that the key will be removed when it expires.
Expiration time precision
Starting from redis2.6, the deviation of expiration time is between 0 and 1 millisecond.
Expiration time logic
The expiration time of the key uses the Unix absolute timestamp (with milliseconds as the precision). Even if the redis instance is closed, by that Unix time If you poke it, the key will also expire (it just won't be cleared immediately).
If you want to move data in one redis to redis on another computer by moving RDB files, you need to ensure that the unix absolute timestamps of the two computers are consistent.
If you set an expiration time for a key, do not modify your computer time casually, because redis will often check the system time. If you adjust the time forward, the keys that should expire will not expire. If you adjust the time backward, keys will expire that shouldn't expire.
How redis cleans up expired keys:
Redis cleans up expired keys in two ways: passive cleaning and active cleaning.
(1) Passive cleaning: When accessing a key with an expiration time, if it is found that the key has expired, the key will be cleared.
(2) redis will perform 10 checks per second, each check includes:
Randomly select 20 keys with expiration time, and then delete them All expired keys.
If more than 25% of the keys among these 20 have expired, then perform step 1) again.
This is a simple probability algorithm, we assume that the selected key can be used as a sample of all keys with expiration time. Through the above operations, we can basically determine that the ratio of timed-out keys to keys with timeout periods is less than 25%. Then the excess memory occupied by expired keys that have not been cleaned up should be less than 25%.
How to handle expiration cleanup in replication and AOF files
In order not to destroy consistency, when a key expires and is cleaned up, the DEL operation will be synchronized with the AOF file and all replica nodes. In this way, the master node is responsible for the expiration cleanup operation. The slave node will not process the expiration cleanup of keys, but will only wait for the DEL command from the master node, so that the key spaces of the master node and the slave node will remain consistent.
For more redis knowledge, please pay attention to the redis introductory tutorial column.
The above is the detailed content of redis key expiration settings. 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 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.

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).

The best way to understand Redis source code is to go step by step: get familiar with the basics of Redis. Select a specific module or function as the starting point. Start with the entry point of the module or function and view the code line by line. View the code through the function call chain. Be familiar with the underlying data structures used by Redis. Identify the algorithm used by Redis.

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.

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)
