Use case settings The following table shows the default use case settings for a Pro database. Type High Availability Data Persistence Capabilities Eviction Policy Cache Single-zone None None volatile-lru Database Multi-zone Append-only file every 1 sec Search & query, JSON, Probabilistic, Time Series None Vector Search Multi-zone Append-only file every 1 sec Search & query, JSON None Custom Single-zone Append-only file every 1 sec None None Billing Unit types The Redis Billing Unit types associated with your Pro subscription depend on your database memory size and throughput requirements. »

Redis contributes extensively to the open source Redis project and uses it inside of Redis Enterprise Software and Redis Cloud. As a rule, we adhere to the open source project’s specifications and update both products with the latest version of open source Redis. Redis commands See Compatibility with open source Redis commands to learn which open source Redis commands are compatible with Redis Enterprise Software and Redis Cloud. Configuration settings Compatibility with open source Redis configuration settings lists the open source Redis configuration settings supported by Redis Enterprise Software and Redis Cloud. »

You can select the tag’s Key and Value from the suggestions, or you can enter your own. A valid tag must follow these guidelines: Tag keys must be between 2 and 64 characters long, and values must be at least 2 characters long. Tags can only have lowercase letters, numbers, spaces, and these special characters: -, _, ., +, @, and :. After you add your first tag, you can: »

If you’ve enabled the database’s CIDR allow list, you must also add the VPC peered IP addresses to the CIDR allow list to connect to the database via the private endpoint. »

To enable TLS for Replica Of cluster connections: For each cluster hosting a replica: Go to Cluster > Security > Certificates. Expand the Replica Of and Active-Active authentication (Syncer certificate) section. Download or copy the syncer certificate. From the Security tab of the Replica Of source database, select Edit. In the TLS - Transport Layer Security for secure connections section, make sure the checkbox is selected. In the Apply TLS for section, select Between databases only. »

To reset a user password from the CLI, run: rladmin cluster reset_password <username> You are asked to enter and confirm the new password. »

heading 1 heading 2 heading 3 cell 1x1 cell 1x2 cell 1x3 cell 2x1 cell 2x2 cell 2x3 Example Shortcode Inside an embedded markdown file. Tip - Another example of shortcode inside an embedded file. »

In addition to the shard placement policy, considerations that determine shard placement are: Separation of master and replica shards Available persistence and Auto Tiering storage Rack-zone awareness Memory available to host the database when fully populated The shard placement policies are: dense - Place as many shards as possible on the smallest number of nodes to reduce the latency between the proxy and the database shards; Recommended for Redis on RAM databases to optimize memory resources sparse - Spread the shards across as many nodes in the cluster as possible to spread the traffic across cluster nodes; Recommended for databases with Auto Tiering enabled to optimize disk resources When you create a Redis Enterprise Software cluster, the default shard placement policy (dense) is assigned to all databases that you create on the cluster. »

Redis Enterprise Software is supported on several operating systems, cloud environments, and virtual environments. Supported platforms ✅ Supported – The platform is supported for this version of Redis Enterprise Software and Redis Stack modules. ⚠️ Deprecation warning – The platform is still supported for this version of Redis Enterprise Software, but support will be removed in a future release. Redis Enterprise major versions 7.4 7.2 6.4 6.2 Release date Feb 2024 Aug 2023 Feb 2023 Aug 2021 End-of-life date Determined after »

To encrypt Replica Of synchronization traffic, you must also configure encryption for the replica database (the destination). Encrypt source synchronization traffic To enable TLS for Replica Of communication only on the source database: In databases, either: Create a new database. Select a database to configure and then select Edit. Enable TLS. Select the communication that you want to secure: For a new database - Require TLS for Replica Of communications only is selected by default. »