Configuration settings

• Database version - The Redis version used by your database.

• Database name - The database name requirements are:

  • Maximum of 63 characters

  • Only letters, numbers, or hyphens (-) are valid characters

  • Must start and end with a letter or digit

  • Case-sensitive

• Port - You can define the port number that clients use to connect to the database. Otherwise, a port is randomly selected.

  Note:

  You cannot change the port number after the database is created.

• Memory limit - Database memory limits include all database replicas and shards, including replica shards in database replication and database shards in database clustering.

  If the total size of the database in the cluster reaches the memory limit, the data eviction policy for the database is enforced.

  Note:

  If you create a database with Auto Tiering enabled, you also need to set the RAM-to-Flash ratio for this database. Minimum RAM is 10%. Maximum RAM is 50%.

• Memory eviction - The default eviction policy for Active-Active databases is noeviction. Redis Enterprise versions 6.0.20 and later support all eviction policies for Active-Active databases, unless Auto Tiering is enabled.

• Capabilities (previously Modules) - When you create a new in-memory database, you can enable multiple Redis Stack capabilities in the database. For Auto Tiering databases, you can enable capabilities that support Auto Tiering. See Redis Enterprise and Redis Stack feature compatibility for compatibility details.

  Note:

  To use Redis Stack capabilities, enable them when you create a new database. You cannot enable them after database creation.

  To add capabilities to the database:

  1. In the Capabilities section, select one or more capabilities.

  2. To customize capabilities, select Parameters and enter the optional custom configuration.

  3. Select Done.

TLS

If you enable TLS when you create the Active-Active database, the nodes use the TLS mode Require TLS for CRDB communication only to require TLS authentication and encryption for communications between participating clusters.

After you create the Active-Active database, you can set the TLS mode to Require TLS for all communications so client communication from applications are also authenticated and encryption.

High availability

• Replication - We recommend that all Active-Active database use replication for best intercluster synchronization performance.

  When replication is enabled, every Active-Active database master shard is replicated to a corresponding replica shard. The replica shards are then used to synchronize data between the instances, and the master shards are dedicated to handling client requests.

• Replica high availability - We also recommend that you enable replica high availability to ensure replica shards are highly-available for this synchronization.

Clustering

• In the Clustering section, you can either:

  • Enable sharding and select the number of shards you want to have in the database. When database clustering is enabled, databases have limitations for multi-key operations.

    You can increase the number of shards in the database at any time.

  • Clear the Enable sharding option to use only one shard, which allows you to use multi-key operations without the limitations.

  Note:

  You cannot enable or turn off database clustering after the Active-Active database is created.

• OSS Cluster API - The OSS Cluster API configuration allows access to multiple endpoints for increased throughput. The OSS Cluster API setting applies to all instances of the Active-Active database across participating clusters.

  This configuration requires clients to connect to the primary node to retrieve the cluster topology before they can connect directly to proxies on each node.

  When you enable the OSS Cluster API, shard placement changes to Sparse, and the database proxy policy changes to All primary shards automatically.

Durability

To protect against loss of data stored in RAM, you can enable Persistence to store a copy of the data on disk.

Active-Active databases support append-only file (AOF) persistence only. Snapshot persistence is not supported for Active-Active databases.

Access control

• Unauthenticated access - You can access the database as the default user without providing credentials.

• Password-only authentication - When you configure a password for your database's default user, all connections to the database must authenticate with the [AUTH command](/commands/auth/.

  If you also configure an access control list, connections can specify other users for authentication, and requests are allowed according to the Redis ACLs specified for that user.

  Creating a database without ACLs enables a default user with full access to the database. You can secure default user access by requiring a password.

• Access Control List - You can specify the user roles that have access to the database and the Redis ACLs that apply to those connections.

  You can only configure access control after the Active-Active database is created. In each participating cluster, add ACLs after database creation.

  To define an access control list for a database:

  1. In Security > Access Control > Access Control List, select + Add ACL.

  2. Select a role to grant database access.

  3. Associate a Redis ACL with the role and database.

  4. Select the check mark to add the ACL.

Causal consistency

Causal consistency in an Active-Active database guarantees that the order of operations on a specific key is maintained across all instances of an Active-Active database.

To enable causal consistency for an existing Active-Active database, use the REST API.

Test Active-Active database connections

With the Redis database created, you are ready to connect to your database. See Connect to Active-Active databases for tutorials and examples of multiple connection methods.