Embeds | IdeaArmor

On the Databases screen, select Quick database. Enter 12000 for the Port. If port 12000 is not available, enter any available port number between 10000 to 19999 or leave it blank to let the cluster assign a port number for you. You will use this port number to connect to the database. Select Create to create your database. When you see Database active appear on the database configuration screen, the database is activated and ready for you to use. »

Redis 7.0 breaking changes When new major versions of open source Redis change existing commands, upgrading your database to a new version can potentially break some functionality. Before you upgrade, make sure to read the provided list of breaking changes that affect Redis Enterprise and update any applications that connect to your database to handle these changes. To check your Redis database version (redis_version), you can use the admin console or run the INFO command with redis-cli: »

Redis 7.2 breaking changes When new major versions of open source Redis change existing commands, upgrading your database to a new version can potentially break some functionality. Before you upgrade, make sure to read the provided list of breaking changes that affect Redis Enterprise and update any applications that connect to your database to handle these changes. Confirm your Redis database version (redis_version) using the admin console or run the following INFO command via redis-cli: »

There are two known limitations for the version of Redis 7.2 that is packaged with Redis Enterprise. Using XREADGROUP BLOCK with > to return all new streams will cause the Redis database to freeze until the shard is restarted (#12031) Because a rejected command does not record the duration for command stats, an error will appear after it is reprocessed that will cause the Redis database to freeze until the shard is restarted (#12247) »

Migration guides for certain clients If you are using Go-Redis v9 or Lettuce v6+, which by default switch to the RESP3 protocol, and you are running Redis Stack commands, please make sure the protocol version is pinned to RESP2 prior to upgrading to Redis version 7.2. Go-Redis For applications using Go-Redis v9 and later, ensure that you have Go-Redis v9.0.5 or newer and pin the protocol version as shown below: »

Select the Cost report button to download a report of all shard costs in CSV format. The report gives a breakdown of all your Redis shard costs, per subscription and database, by month. Subscriptions under the minimum subscription price are broken down into actual shard prices and the difference from minimum price. »

Before creating a Redis Cloud database, you need to create an account. To create a database in your Redis Cloud account: Sign in to the Redis Cloud console. Select the New database button. This displays the Create database screen. Select your Redis use case. There are four pre-defined use cases: Cache: Stores short-term or volatile data. Can be used for session management, semantic cache, session store, and other uses where data is short-lived. »

As of January 2024, new and upgraded Redis Cloud Essentials subscriptions are limited to one database per subscription. If you have a Redis Cloud Essentials subscription created before January 2024, you can add databases up to the previous plan limit. If you choose to upgrade your plan, you can keep your databases, but you will need to create a new subscription to add another database. »

Select Opt-in to 7.2 to request to upgrade your subscription and databases to Redis 7.2 (Redis 6.2 and earlier only). The upgrade will start one week from your request, according to maintenance windows. Redis 7.2 introduces several changes to existing Redis commands; see the list of breaking changes for more details. »