All Products
Search
Document Center

ApsaraDB for Redis:New features and compatibility changes of major versions of Redis

Last Updated:Aug 22, 2023

In ApsaraDB for Redis, you can create ApsaraDB for Redis Community Edition instances of different versions. This topic describes the new features and compatibility changes in each version of ApsaraDB for Redis.

Note

Each section in this topic includes the features and compatibility changes that are provided by the Redis community and Alibaba Cloud.

Redis 7.0

New features

  • For information about the new features of Redis 7.0, see Redis 7.0 release notes.

    • For example, for module commands that use background threads, the slow log feature records the entire time for which a command is run, including suspension time that may occur during command execution. For common block commands such as BLPOP, the slow log feature records only the actual execution time of a command.

Compatibility

Redis 6.0

New features

  • For information about the new features of Redis 6.0, see Redis 6.0 release notes.

  • Within a cluster instance in direct connection mode, PUBLISH commands are broadcast to all nodes.

Compatibility

  • For information about the breaking changes for new Redis 6.0 features, see Redis 6.0 release notes.

  • The account management mechanism of ApsaraDB for Redis is different from the access control list (ACL) feature of open source Redis. The following information describes the account management mechanism of ApsaraDB for Redis:

    • Two accounts are available for an instance: the default account named default and the account that is named after the instance name such as r-bp1857n194kiuv****.

    • If you do not specify an account when you use the AUTH command to connect to an ApsaraDB for Redis instance, the default account is used for authentication.

    • If the account that you specified does not exist when you use the AUTH command to connect to an ApsaraDB for Redis instance, the -WRONGPASS invalid username-password pair error message is returned. In this case, the system does not switch to the default account for authentication.

    • If the account that you specified does not exist or the password that you specified is incorrect when you use the AUTH command to connect to an ApsaraDB for Redis instance that is deployed in a virtual private cloud (VPC) and has password-free access enabled, the -WRONGPASS invalid username-password pair error message instead of OK is returned.

  • You must specify configuration options for the CONFIG GET command. Wildcard characters (*) are not supported.

  • For information about the supported commands, see Commands supported by ApsaraDB for Redis Community Edition.

Redis 5.0

New features

  • For information about the new features of Redis 5.0, see Redis 5.0 release notes.

  • The latency insights feature is supported.

  • The real-time key statistics feature is supported.

  • TLS encryption is supported.

  • The precision of wake-up time for processing blocking connections is optimized.

  • Cluster instances in direct connection mode can be scaled without perceptible impacts on your business.

Compatibility

  • For information about the breaking changes for new Redis 5.0 features, see Redis 5.0 release notes.

    • For example, the results that are returned by commands in Lua scripts are no longer sorted.

  • After you enable password-free access for an instance, you can use the AUTH command to switch between different accounts to connect to the instance without the need to use passwords.

    Note

    If you granted different permissions to different accounts, make sure that your application runs commands within the scope of the permissions. Otherwise, an insufficient permissions error occurs.

  • The READONLY and READWRITE commands are available.

  • Differences exist between instances that use cloud disks and instances that use local disks: After you enable password-free access for an instance that uses cloud disks, all connections to the instance still need to be verified against a whitelist, and the #no_loose_check-whitelist-always parameter cannot be configured.

  • For information about the supported commands, see Commands supported by ApsaraDB for Redis Community Edition.

Redis 4.0

New features

  • For information about the new features of Redis 4.0, see Redis 4.0 release notes.

  • The audit log feature is supported.

  • The real-time hotkey statistics feature is supported.

  • After you enable password-free access for an instance that is deployed in a VPC, you can configure #no_loose_check-whitelist-always to specify whether to verify connections from within the same VPC against a whitelist. For more information, see Supported parameters.

  • The Sentinel-compatible mode is supported. You must enable password-free access to use this mode. Only the SENTINEL and get-master-addr-by-name subcommands are supported.

  • You can create multiple accounts and grant read/write or read-only permissions to the accounts. You can use the AUTH user:password command to switch between accounts.

    • The name of the default account is the instance name, such as r-bp1857n194kiuv****.

    • If you do not specify an account or the account that you specified does not exist, the system switches to the default account for authentication.

    • If you enable password-free access for an instance, no authentication is required for all connections to the instance. The default account is used, and cannot be switched to another account.

  • You can enable the direct connection mode for the cluster architecture.

  • The cluster architecture allows you to configure ptod_enabled to pass through client IP addresses to data nodes. For more information, see Supported parameters.

Compatibility

  • For information about the breaking changes for new Redis 4.0 features, see Redis 4.0 release notes.

    • For example, slot-to-key mappings must be recorded in the cluster architecture, which results in slightly higher memory usage for identical data compared to the standard architecture.

    • For example, the SORT command does not support the BY and GET parameters in cluster instances.

  • SSL encryption is no longer supported.

  • Cluster instances in direct connection mode do not support specific CLUSTER commands. For more information, see Commands supported by ApsaraDB for Redis Community Edition.

  • Cluster instances in direct connection mode support the SELECT command.

    Note

    You can no longer use the SELECT command to determine whether the current connection is in cluster mode. If you use the SELECT command, a false positive may occur.

  • Within a cluster instance in direct connection mode, PUBLISH commands in a node are not broadcast to other nodes.

  • For information about the supported commands, see Commands supported by ApsaraDB for Redis Community Edition.

Redis 2.8 (discontinued)

New features

  • For information about the new features of Redis 2.8, see Redis 2.8 release notes.

  • You can configure whitelists for instances. For more information, see Step 2: Configure whitelists.

  • You can enable password-free access for instances that are deployed in a VPC. After you enable this feature, the following situations apply:

    • IP address whitelist verification is not required for network connections from within the VPC.

    • When you use the AUTH command to authenticate network connections from within the VPC, OK is returned without the need for password verification.

  • SSL encryption is supported.

  • You can configure a parameter to disable specific commands. For more information, see Disable high-risk commands.

  • Cluster instances in proxy mode are supported.

Compatibility

  • For information about the breaking changes for new Redis 2.8 features, see Redis 2.8 release notes.

  • Specific debugging commands and management commands are not supported. For more information, see Commands supported by ApsaraDB for Redis Community Edition.

  • The CONFIG SET and CONFIG GET commands return limited information:

    • CONFIG GET: returns only partial configuration options. Security-related configuration options are not returned.

    • CONFIG SET: returns OK without modifying parameters.

  • The INFO command returns limited information. For example, security-related information such as Persistence and Replication is not returned.

  • Cluster instances in proxy mode do not support specific commands. For more information, see Limits on commands supported by cluster instances.