Release Notes
Announcements
N in the O(N) commandHGETALL, IRANGE, SMEMBERS, ZRANGE, and sinter . When using them, you need to specify the value of N.HSCAN, SSCAN, and ZSCAN commands in Redis can be used to traverse hash tables, sets, and sorted sets. These commands allow you to scan elements in the data set by using an iterator, without returning all elements at once like HGETALL, SMEMBERS, and ZRANGE. When using these commands, we recommend that you specify an appropriate COUNT parameter to avoid Redis performance degradation caused by excessive returned elements at once. Returning 1000 elements per traversal is preferred, but the specific quantity depends on the actual Redis situation. You can adjust it as needed.KEYS, FLUSHALL, FLUSHDB are not allowed as the single-threaded CRedis takes a long time to execute them, which may cause command execution blocking. To address the potential blocking, we recommend that you use the scan command in a progressive manner or configure the disabled commands by disable-command-list parameter.FLUSHDB and FLUSHALL: We recommend that you not use these two commands in the production environment, as they will clear all data in Redis.KEYS: It returns all keys matched with specified mode. We recommend that you not use this command in the production environment, as it will block Redis server.RANDOMKEY: It returns one key randomly. We recommend that you not use this command in the production environment, as it will block Redis server.INFO: It returns various statistics and configuration items of the Redis server. We recommend that you not use this command in the production environment, as it will block Redis server.CONFIG: It allows you to modify the configuration items of the Redis server. But use it with caution as it may cause server to crash.SHUTDOWN: It allows you to disable the Redis server. We recommend that you not use this command in the production environment, as it will cause data loss.BGREWRITEAOF and BGSAVE: It allows you to asynchronously rewrite the AOF and RDB files with a large amount of system resources being consumed. So use it with caution.SELECT command. The index number of each database is specified by a digit that starts from 0.GET or SET operations, you can use mget and mset for batch data operations to reduce the network RTT. The number of elements in MGET and MGET operations should not exceed 500. The greater this number is, the greater the impact will be in the case of jitter or scaling on the backend.MEGET, MESETmset.PIPELINE, which improves efficiency.big key in the elements of batch operation.PIPELINEis not.PIPELINE allows you to pack multiple commands,while the native command not.PIPELINE must be supported on client and server.Luaredis.call/pcall, the key must be in the KEYS array. Otherwise, the following error message will be returned: error，"-ERR bad lua script for redis cluster,all the keys that the script uses should be passed using the KEYS array".error, "-ERR eval/evalsha command keys must in same slotrn".MONITOR commandMONITOR command has some impacts on the performance of Redis. In daily usage, it is used only for analyzing command execution and not for monitoring. We recommend that you enable it only in the case of troubleshooting or analysis, and disable it in time.피드백