diff --git a/content/operate/_index.md b/content/operate/_index.md index 2ed166aaae..4fb71dccc7 100644 --- a/content/operate/_index.md +++ b/content/operate/_index.md @@ -24,7 +24,7 @@ hideListLinks: true | Replication | [Replication]({{< relref "/operate/rc/databases/configuration/high-availability" >}}) | [Replication]({{}}) | [Replication]({{< relref "/operate/oss_and_stack/management/replication" >}}) | [Create replica databases]({{}})| | Active-Active geo-distribution | [Active-Active Redis]({{< relref "/operate/rc/databases/configuration/active-active-redis" >}}) | [Active-Active Redis]({{}}) | | [Active-Active databases]({{}}) | | Rolling upgrades | [Upgrade database version]({{< relref "/operate/rc/databases/upgrade-version" >}}) | [Upgrade Redis Software]({{}}) | | [Upgrade Redis for K8s]({{}}) | -| Redis Flex/Auto tiering | [Create a Redis Flex database]({{< relref "/operate/rc/databases/create-database/create-flex-database" >}}) | [Auto Tiering]({{}}) | | [Auto Tiering]({{}}) | +| Redis Flex/Auto tiering | [Create a Redis Flex database]({{< relref "/operate/rc/databases/create-database/create-flex-database" >}}) | [Redis Flex]({{}}) | | [Auto Tiering]({{}}) | | Persistence | [Data persistence]({{< relref "/operate/rc/databases/configuration/data-persistence" >}}) | [Persistence]({{}}) | [Persistence]({{< relref "/operate/oss_and_stack/management/replication" >}}) | [Persistence volumes]({{}})| | Recovery | Automatic | [Recover cluster]({{}}) | [Manual failover]({{< relref "/operate/oss_and_stack/management/scaling#manual-failover" >}}) | [Cluster recovery]({{}}) | | Backups | [Back up a database]({{< relref "/operate/rc/databases/back-up-data" >}}) | [Schedule backups]({{}}) | [Persistence]({{< relref "/operate/oss_and_stack/management/replication" >}}) | [REDB spec.backup]({{}}) | diff --git a/content/operate/rc/databases/configuration/data-eviction-policies.md b/content/operate/rc/databases/configuration/data-eviction-policies.md index e29f399ab3..c50de91b20 100644 --- a/content/operate/rc/databases/configuration/data-eviction-policies.md +++ b/content/operate/rc/databases/configuration/data-eviction-policies.md @@ -35,7 +35,7 @@ For each database, you can choose from these data eviction policies: ## Prevent data eviction -Redis Cloud supports [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) +Redis Cloud supports [Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}) to prevent data eviction but maintain high performance. Auto Tiering can extend your database across RAM and Flash Memory and intelligently manage "hot" (active) data in RAM and "cold" (less active) data in Flash memory (SSD). diff --git a/content/operate/rc/databases/create-database/create-pro-database-new.md b/content/operate/rc/databases/create-database/create-pro-database-new.md index 6704397e3f..3a96c77e73 100644 --- a/content/operate/rc/databases/create-database/create-pro-database-new.md +++ b/content/operate/rc/databases/create-database/create-pro-database-new.md @@ -130,7 +130,7 @@ The following settings are defined in the **Advanced options** of the **Setup** | **Public endpoint access** | Select whether or not to [block public endpoints]({{< relref "/operate/rc/security/database-security/block-public-endpoints" >}}) for all databases in the subscription. | | **VPC configuration** | Select **In a new VPC** to deploy to a new [virtual private cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud) (VPC).

To deploy these databases to an existing virtual private cloud, select **In existing VPC** and then set VPC ID to the appropriate ID value.

(Available only if [Redis Cloud Bring your own Cloud]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud" >}}) is enabled) | | **Deployment CIDR** | The [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) range of IP addresses for your deployment. Redis creates a new [subnet](https://en.wikipedia.org/wiki/Subnetwork) for the **Deployment CIDR** in your [virtual private cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud) (VPC). It cannot overlap with the CIDR ranges of other subnets used by your account.

For deployments in an existing VPC, the **Deployment CIDR** must be within your VPC's **primary** CIDR range (secondary CIDRs are not supported). | -| **Auto Tiering**| Determines if your databases are stored only in memory (RAM) or are split between memory and Flash storage (RAM+Flash). See [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}})| +| **Auto Tiering**| Determines if your databases are stored only in memory (RAM) or are split between memory and Flash storage (RAM+Flash). See [Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}})| | **Maintenance windows** | Determines when Redis can perform [maintenance]({{< relref "/operate/rc/subscriptions/maintenance" >}}) on your databases. Select **Manual** if you want to set [manual maintenance windows]({{< relref "/operate/rc/subscriptions/maintenance/set-maintenance-windows" >}}). | When finished, choose **Continue** to determine your size requirements. diff --git a/content/operate/rs/7.4/databases/auto-tiering/_index.md b/content/operate/rs/7.4/databases/auto-tiering/_index.md index f5d67e68ea..aa15bab63f 100644 --- a/content/operate/rs/7.4/databases/auto-tiering/_index.md +++ b/content/operate/rs/7.4/databases/auto-tiering/_index.md @@ -11,6 +11,7 @@ hideListLinks: true linktitle: Auto Tiering weight: 50 url: '/operate/rs/7.4/databases/auto-tiering/' +aliases: /operate/rs/7.4/databases/flash/ --- Redis Enterprise's auto tiering offers users the unique ability to use solid state drives (SSDs) to extend databases beyond DRAM capacity. Developers can build applications that require large datasets using the same Redis API. diff --git a/content/operate/rs/7.4/databases/auto-tiering/quickstart.md b/content/operate/rs/7.4/databases/auto-tiering/quickstart.md index 4b24acd33d..74a888833e 100644 --- a/content/operate/rs/7.4/databases/auto-tiering/quickstart.md +++ b/content/operate/rs/7.4/databases/auto-tiering/quickstart.md @@ -10,6 +10,7 @@ description: Get started with Auto Tiering quickly, creating a cluster and datab linkTitle: Quick start weight: 80 url: '/operate/rs/7.4/databases/auto-tiering/quickstart/' +aliases: /operate/rs/7.4/databases/flash/quickstart/ --- This page guides you through a quick setup of [Auto Tiering]({{< relref "/operate/rs/7.4/databases/auto-tiering/" >}}) with a single node for testing and demo purposes. diff --git a/content/operate/rs/7.4/databases/auto-tiering/storage-engine.md b/content/operate/rs/7.4/databases/auto-tiering/storage-engine.md index 91e3af4256..b082c372d2 100644 --- a/content/operate/rs/7.4/databases/auto-tiering/storage-engine.md +++ b/content/operate/rs/7.4/databases/auto-tiering/storage-engine.md @@ -9,6 +9,7 @@ description: Manage the storage engine used for your database with auto tiering linkTitle: Manage storage engine weight: 100 url: '/operate/rs/7.4/databases/auto-tiering/storage-engine/' +aliases: /operate/rs/7.4/databases/flash/storage-engine/ --- ## Manage the storage engine diff --git a/content/operate/rs/7.8/databases/auto-tiering/_index.md b/content/operate/rs/7.8/databases/auto-tiering/_index.md index 4f761e4e54..fd8ec71407 100644 --- a/content/operate/rs/7.8/databases/auto-tiering/_index.md +++ b/content/operate/rs/7.8/databases/auto-tiering/_index.md @@ -11,6 +11,7 @@ hideListLinks: true linktitle: Auto Tiering weight: 50 url: '/operate/rs/7.8/databases/auto-tiering/' +aliases: /operate/rs/7.8/databases/flash/ --- Redis Enterprise's auto tiering offers users the unique ability to use solid state drives (SSDs) to extend databases beyond DRAM capacity. Developers can build applications that require large datasets using the same Redis API. diff --git a/content/operate/rs/7.8/databases/auto-tiering/quickstart.md b/content/operate/rs/7.8/databases/auto-tiering/quickstart.md index f50d6434d0..46df1434aa 100644 --- a/content/operate/rs/7.8/databases/auto-tiering/quickstart.md +++ b/content/operate/rs/7.8/databases/auto-tiering/quickstart.md @@ -10,6 +10,7 @@ description: Get started with Auto Tiering quickly, creating a cluster and datab linkTitle: Quick start weight: 80 url: '/operate/rs/7.8/databases/auto-tiering/quickstart/' +aliases: /operate/rs/7.8/databases/flash/quickstart/ --- This page guides you through a quick setup of [Auto Tiering]({{< relref "/operate/rs/7.8/databases/auto-tiering/" >}}) with a single node for testing and demo purposes. diff --git a/content/operate/rs/7.8/databases/auto-tiering/storage-engine.md b/content/operate/rs/7.8/databases/auto-tiering/storage-engine.md index b4dec2004e..58acafd948 100644 --- a/content/operate/rs/7.8/databases/auto-tiering/storage-engine.md +++ b/content/operate/rs/7.8/databases/auto-tiering/storage-engine.md @@ -9,6 +9,7 @@ description: Manage the storage engine used for your database with auto tiering linkTitle: Manage storage engine weight: 100 url: '/operate/rs/7.8/databases/auto-tiering/storage-engine/' +aliases: /operate/rs/7.8/databases/flash/storage-engine/ --- ## Manage the storage engine diff --git a/content/operate/rs/clusters/add-node.md b/content/operate/rs/clusters/add-node.md index e97a7f51da..d2c44ee738 100644 --- a/content/operate/rs/clusters/add-node.md +++ b/content/operate/rs/clusters/add-node.md @@ -63,7 +63,7 @@ with a custom certificate. 1. Enter a path for [*Persistent storage*]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}), or leave the default path. - 1. To enable [*Auto Tiering*]({{< relref "/operate/rs/databases/auto-tiering/" >}}), + 1. To enable [*Redis Flex or Auto Tiering*]({{< relref "/operate/rs/databases/flash/" >}}), select **Enable flash storage** and enter the path to the flash storage. 1. If the cluster is configured to support [rack-zone awareness]({{< relref "/operate/rs/clusters/configure/rack-zone-awareness.md" >}}), set the **Rack-zone ID** for the new node. diff --git a/content/operate/rs/clusters/new-cluster-setup.md b/content/operate/rs/clusters/new-cluster-setup.md index bcbeee6c35..dc9626a609 100644 --- a/content/operate/rs/clusters/new-cluster-setup.md +++ b/content/operate/rs/clusters/new-cluster-setup.md @@ -57,7 +57,7 @@ To create a cluster: 1. Enter a path for [*Persistent storage*]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}), or leave the default path. - 1. To enable [*Auto Tiering*]({{< relref "/operate/rs/databases/auto-tiering/" >}}), + 1. To enable [*Redis Flex or Auto Tiering*]({{< relref "/operate/rs/databases/flash/" >}}), select **Enable flash storage** and enter the path to the flash storage. 1. If the cluster is configured to support [rack-zone awareness]({{< relref "/operate/rs/clusters/configure/rack-zone-awareness.md" >}}), set the **Rack-zone ID** for the new node. diff --git a/content/operate/rs/clusters/replace-node.md b/content/operate/rs/clusters/replace-node.md index 2b44e9daca..7965dc6cbd 100644 --- a/content/operate/rs/clusters/replace-node.md +++ b/content/operate/rs/clusters/replace-node.md @@ -19,7 +19,7 @@ To replace a failed node: configure Redis Enterprise Software on the node. See [Install and setup]({{< relref "/operate/rs/installing-upgrading" >}}) for more information. {{< note >}} -If you are using [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}), make sure the required flash storage is set up on this new node. +If you are using [Redis Flex or Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}), make sure the required flash storage is set up on this new node. {{< /note >}} 1. [Add the node]({{< relref "/operate/rs/clusters/add-node" >}}) to the cluster. Make sure the new node has as much available memory as the faulty diff --git a/content/operate/rs/databases/active-active/create.md b/content/operate/rs/databases/active-active/create.md index 2fdda48049..434ef72442 100644 --- a/content/operate/rs/databases/active-active/create.md +++ b/content/operate/rs/databases/active-active/create.md @@ -87,14 +87,14 @@ Every instance of an Active-Active database can receive write operations, and al {{Add cluster panel.}} {{}} -If an Active-Active database [runs on flash memory]({{}}), you cannot add participating clusters that run on RAM only. +If an Active-Active database [runs on flash memory]({{}}), you cannot add participating clusters that run on RAM only. {{}} 1. Click **Join cluster** to add the cluster to the list of participating clusters. 1. Enter a **Database name**. -1. If your cluster supports [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}), in **Runs on** you can select **Flash** so that your database uses Flash memory. We recommend that you use AOF every 1 sec for the best performance during the initial Active-Active database sync of a new replica. +1. If your cluster supports [Redis Flex or Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}), in **Runs on** you can select **Flash** so that your database uses Flash memory. We recommend that you use AOF every 1 sec for the best performance during the initial Active-Active database sync of a new replica. 1. To configure additional database settings, expand each relevant section to make changes. @@ -132,7 +132,7 @@ If you create a database with Auto Tiering enabled, you also need to set the RAM for this database. Minimum RAM is 10%. Maximum RAM is 50%. {{< /note >}} -- **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. +- **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 [Redis Flex or Auto Tiering]({{}}) is enabled. - [**Capabilities**]({{< relref "/operate/oss_and_stack/stack-with-enterprise" >}}) (previously **Modules**) - When you create a new in-memory database, you can enable additional capabilities in the database. You cannot enable them after database creation. diff --git a/content/operate/rs/databases/active-active/develop/develop-for-aa.md b/content/operate/rs/databases/active-active/develop/develop-for-aa.md index fe063cc95e..4cd067baeb 100644 --- a/content/operate/rs/databases/active-active/develop/develop-for-aa.md +++ b/content/operate/rs/databases/active-active/develop/develop-for-aa.md @@ -97,7 +97,7 @@ execute them in script-replication mode. ## Eviction -The default policy for Active-Active databases is _noeviction_ mode. Redis Enterprise version 6.0.20 and later support all eviction policies for Active-Active databases, unless [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering" >}})(previously known as Redis on Flash) is enabled. +The default policy for Active-Active databases is _noeviction_ mode. Redis Enterprise version 6.0.20 and later support all eviction policies for Active-Active databases, unless [Redis Flex or Auto Tiering]({{< relref "/operate/rs/databases/flash" >}})(previously known as Redis on Flash) is enabled. For details, see [eviction for Active-Active databases]({{< relref "/operate/rs/databases/memory-performance/eviction-policy#active-active-database-eviction" >}}). diff --git a/content/operate/rs/databases/active-active/manage.md b/content/operate/rs/databases/active-active/manage.md index 8c5b76da1f..0785cacd05 100644 --- a/content/operate/rs/databases/active-active/manage.md +++ b/content/operate/rs/databases/active-active/manage.md @@ -35,7 +35,7 @@ the new database instance can accept connections and read operations. The new instance does not accept write operations until it is in the syncing state. {{}} -If an Active-Active database [runs on flash memory]({{}}), you cannot add participating clusters that run on RAM only. +If an Active-Active database [runs on flash memory]({{}}), you cannot add participating clusters that run on RAM only. {{}} To add a new participating cluster to an existing Active-Active configuration using the Cluster Manager UI: diff --git a/content/operate/rs/databases/active-active/planning.md b/content/operate/rs/databases/active-active/planning.md index 54c2d4f825..3ea62f15a6 100644 --- a/content/operate/rs/databases/active-active/planning.md +++ b/content/operate/rs/databases/active-active/planning.md @@ -22,7 +22,7 @@ See [Active-Active Redis]({{< relref "/operate/rs/databases/active-active/" >}}) You need at least [two participating clusters]({{< relref "/operate/rs/clusters/new-cluster-setup" >}}) for an Active-Active database. If your database requires more than ten participating clusters, contact Redis support. You can [add or remove participating clusters]({{< relref "/operate/rs/databases/active-active/manage#participating-clusters/" >}}) after database creation. {{}} -If an Active-Active database [runs on flash memory]({{}}), you cannot add participating clusters that run on RAM only. +If an Active-Active database [runs on flash memory]({{}}), you cannot add participating clusters that run on RAM only. {{}} Changes made from the Cluster Manager UI to an Active-Active database configuration only apply to the cluster you are editing. For global configuration changes across all clusters, use the `crdb-cli` command-line utility. @@ -86,4 +86,4 @@ Active-Active databases have the following limitations: - The `UNLINK` command is a blocking command for all types of keys. - Cross slot multi commands (such as `MSET`) are not supported with Active-Active databases. - The hashing policy can't be changed after database creation. -- If an Active-Active database [runs on flash memory]({{}}), you cannot add participating clusters that run on RAM only. +- If an Active-Active database [runs on flash memory]({{}}), you cannot add participating clusters that run on RAM only. diff --git a/content/operate/rs/databases/configure/database-persistence.md b/content/operate/rs/databases/configure/database-persistence.md index 7bf2810ff7..b88cffcc2d 100644 --- a/content/operate/rs/databases/configure/database-persistence.md +++ b/content/operate/rs/databases/configure/database-persistence.md @@ -11,7 +11,7 @@ linktitle: Persistence weight: 30 --- -Data is stored in RAM or a combination of RAM and flash memory ([Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}})), which risks data loss during process or server failures. Redis Enterprise Software supports multiple methods to persist data to disk on a per-database basis to ensure data durability. +Data is stored in RAM or a combination of RAM and flash memory ([Redis Flex and Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}})), which risks data loss during process or server failures. Redis Enterprise Software supports multiple methods to persist data to disk on a per-database basis to ensure data durability. You can configure [persistence](https://redis.com/redis-enterprise/technology/durable-redis/) during database creation or by editing an existing database. Although the persistence model can be changed dynamically, the switch can take time depending on the database size and the models being switched. diff --git a/content/operate/rs/databases/auto-tiering/_index.md b/content/operate/rs/databases/flash/_index.md similarity index 54% rename from content/operate/rs/databases/auto-tiering/_index.md rename to content/operate/rs/databases/flash/_index.md index 1f50abba7e..b5c1222f87 100644 --- a/content/operate/rs/databases/auto-tiering/_index.md +++ b/content/operate/rs/databases/flash/_index.md @@ -1,52 +1,67 @@ --- -Title: Auto Tiering +Title: Redis Flex and Auto Tiering alwaysopen: false categories: - docs - operate - rs - rc -description: Auto Tiering enables your data to span both RAM and dedicated flash memory. +description: Redis Flex and Auto Tiering enable your data to span both RAM and dedicated flash memory. hideListLinks: true -linktitle: Auto Tiering +linktitle: Redis Flex and Auto Tiering weight: 50 +aliases: /operate/rs/databases/auto-tiering/ --- -Redis Enterprise's auto tiering offers users the unique ability to use solid state drives (SSDs) to extend databases beyond DRAM capacity. +Redis Flex and Auto Tiering in Redis Enterprise Software enable databases to use solid state drives (SSDs) to extend beyond DRAM capacity. Developers can build applications that require large datasets using the same Redis API. Using SSDs can significantly reduce the infrastructure costs compared to only DRAM deployments. Frequently used data, called hot data, belongs in the fastest memory level to deliver a real-time user experience. Data that is accessed less frequently, called warm data, can be kept in a slightly slower memory tier. -Redis Enterprise’s Auto tiering maintains hot data in DRAM, keeps warm data in SSDs, and transfers data between tiers automatically. +Redis Flex maintains hot data in DRAM, keeps warm data in SSDs, and transfers data between tiers automatically. -Redis Enterprise’s auto tiering is based on a high-performance storage engine (Speedb) that manages the complexity of using SSDs and DRAM as the total available memory for databases in a Redis Enterprise cluster. This implementation offers a performance boost of up to 10k operations per second per core of the database, doubling the performance of Redis on Flash. +Redis Flex is based on a high-performance storage engine (Speedb) that manages the complexity of using SSDs and DRAM as the total available memory for databases in a Redis Enterprise cluster. This implementation offers a performance boost of up to 10k operations per second per core of the database, doubling the performance of Redis on Flash. -Just like all-RAM databases, databases with Auto Tiering enabled are compatible with existing Redis applications. +Just like all-RAM databases, Redis Flex databases are compatible with existing Redis applications. -Auto Tiering is also supported on [Redis Cloud]({{< relref "/operate/rc/" >}}) and [Redis Enterprise Software for Kubernetes]({{< relref "/operate/rs/" >}}). +Redis Flex is also supported on [Redis Cloud]({{< relref "/operate/rc/" >}}) and [Redis Enterprise Software for Kubernetes]({{< relref "/operate/rs/" >}}). + +## Redis Flex versus Auto Tiering + +Redis Flex is the enhanced successor to Auto Tiering, generally available as of Redis Enterprise Software version 8.0.2. + +Redis database versions support Redis Flex and Auto Tiering as follows: + +| Redis database version | Redis Flex | Auto Tiering | +|------------------------|------------|--------------| +| 8.0 and later | ✅ | ❌ | +| 7.4 | ✅ | ✅| +| 7.2 and earlier | ❌ | ✅ | + +Redis Flex requires the Speedb driver, while Auto Tiering can use either RocksDB or Speedb. See [Manage Auto Tiering storage engine]({{}}) for more information. ## Use cases -The benefits associated with Auto Tiering are dependent on the use case. +The benefits associated with Redis Flex are dependent on the use case. -Auto Tiering is ideal when your: +Redis Flex is ideal when your: - working set is significantly smaller than your dataset (high RAM hit rate) - average key size is smaller than average value size (all key names are stored in RAM) - most recent data is the most frequently used (high RAM hit rate) -Auto Tiering is not recommended for: +Redis Flex is not recommended for: - Long key names (all key names are stored in RAM) - Broad access patterns (any value could be pulled into RAM) - Large working sets (working set is stored in RAM) - Frequently moved data (moving to and from RAM too often can impact performance) -Auto Tiering is not intended to be used for persistent storage. Redis Enterprise Software database persistent and ephemeral storage should be on different disks, either local or attached. +Redis Flex is not intended to be used for persistent storage. Redis Enterprise Software database persistent and ephemeral storage should be on different disks, either local or attached. ## Where is my data? -When using Auto Tiering, RAM storage holds: +When using Redis Flex, RAM storage holds: - All keys (names) - Key indexes - Dictionaries @@ -56,7 +71,7 @@ All data is accessed through RAM. If a value in flash memory is accessed, it bec Inactive or infrequently accessed data is referred to as "warm data" and stored in flash memory. When more space is needed in RAM, warm data is moved from RAM to flash storage. -{{}} When using Auto Tiering with RediSearch, it’s important to note that RediSearch indexes are also stored in RAM.{{}} +{{}} When using Redis Flex with RediSearch, it’s important to note that RediSearch indexes are also stored in RAM.{{}} ## RAM to Flash ratio @@ -67,19 +82,19 @@ The RAM limit cannot be smaller than 10% of the total memory. We recommend you k ## Flash memory -Implementing Auto Tiering requires pre planning around memory and sizing. Considerations and requirements for Auto Tiering include: +Implementing Redis Flex requires pre planning around memory and sizing. Considerations and requirements for Redis Flex include: - Flash memory must be locally attached. Using network-attached storage (NAS), storage area networks (SAN), or solutions such as AWS Elastic Block Storage (EBS) is not supported. -- Flash memory must be dedicated to Auto Tiering and not shared with other parts of the database, such as durability, binaries, or persistence. +- Flash memory must be dedicated to Redis Flex and not shared with other parts of the database, such as durability, binaries, or persistence. - For the best performance, the SSDs should be NVMe based, but SATA can also be used. - The available flash space must be greater than or equal to the total database size (RAM+Flash). The extra space accounts for write buffers and [write amplification](https://en.wikipedia.org/wiki/Write_amplification). {{}} The Redis Enterprise Software database persistent and ephemeral storage should be on different disks, either local or attached. {{}} -Once these requirements are met, you can create and manage both databases with Auto Tiering enabled and +After these requirements are met, you can create and manage both Redis Flex databases and all-RAM databases in the same cluster. -When you begin planning the deployment of an Auto Tiering enabled database in production, +When you begin planning the deployment of a Redis Flex database in production, we recommend working closely with the Redis technical team for sizing and performance tuning. ### Cloud environments @@ -94,7 +109,7 @@ We specifically recommend "[Storage Optimized I4i - High I/O Instances](https:// ### On-premises environments -When you begin planning the deployment of Auto Tiering in production, we recommend working closely with the Redis technical team for sizing and performance tuning. +When you begin planning the deployment of Redis Flex in production, we recommend working closely with the Redis technical team for sizing and performance tuning. On-premises environments support more deployment options than other environments such as: @@ -105,13 +120,13 @@ On-premises environments support more deployment options than other environments - [Probabilistic data structures]({{< relref "/operate/oss_and_stack/stack-with-enterprise/bloom" >}}) -{{}} Enabling Auto Tiering for [Active-Active distributed databases]({{}}) requires validating and getting the Redis technical team's approval first . {{}} +{{}}You should get the Redis technical team's approval before you enable Redis Flex for [Active-Active distributed databases]({{}}). {{}} -{{}} Auto Tiering is not supported running on network attached storage (NAS), storage area network (SAN), or with local HDD drives. {{}} +{{}} Redis Flex is not supported running on network attached storage (NAS), storage area network (SAN), or with local HDD drives. {{}} ## Size limits for keys and values -Auto Tiering databases cannot store keys or values larger than 4GB in flash storage. +Redis Flex databases cannot store keys or values larger than 4GB in flash storage. Keys or values larger than 4GB will be stored in RAM only, and warnings will appear in the Redis logs similar to: @@ -121,8 +136,8 @@ Keys or values larger than 4GB will be stored in RAM only, and warnings will app ## Next steps -- [Auto Tiering metrics]({{< relref "/operate/rs/references/metrics/auto-tiering" >}}) -- [Auto Tiering quick start]({{< relref "/operate/rs/databases/auto-tiering/quickstart.md" >}}) +- [Redis Flex metrics]({{< relref "/operate/rs/references/metrics/auto-tiering" >}}) +- [Redis Flex quick start]({{< relref "/operate/rs/databases/flash/quickstart" >}}) - [Ephemeral and persistent storage]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}) - [Hardware requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}) diff --git a/content/operate/rs/databases/auto-tiering/quickstart.md b/content/operate/rs/databases/flash/quickstart.md similarity index 77% rename from content/operate/rs/databases/auto-tiering/quickstart.md rename to content/operate/rs/databases/flash/quickstart.md index 48a02b4f63..e6c40b4b23 100644 --- a/content/operate/rs/databases/auto-tiering/quickstart.md +++ b/content/operate/rs/databases/flash/quickstart.md @@ -1,26 +1,27 @@ --- -Title: Auto Tiering quick start +Title: Redis Flex and Auto Tiering quick start alwaysopen: false categories: - docs - operate - rs -description: Get started with Auto Tiering quickly, creating a cluster and database +description: Get started with Redis Flex and Auto Tiering quickly, creating a cluster and database using flash storage. linkTitle: Quick start weight: 80 +aliases: /operate/rs/databases/auto-tiering/quickstart/ --- -This page guides you through a quick setup of [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) with a single node for testing and demo purposes. +This page guides you through a quick setup of [Redis Flex and Auto Tiering]({{< relref "/operate/rs/databases/flash" >}}) with a single node for testing and demo purposes. For production environments, you can find more detailed installation instructions in the [install and setup]({{< relref "/operate/rs/installing-upgrading" >}}) section. -The steps to set up a Redis Enterprise Software cluster using Auto Tiering +The steps to set up a Redis Enterprise Software cluster using Redis Flex with a single node are: 1. Install Redis Enterprise Software or run it in a Docker container. -1. Set up a Redis Enterprise Software cluster with Auto Tiering. -1. Create a new database with Auto Tiering enabled. +1. Set up a Redis Enterprise Software cluster with Redis Flex. +1. Create a new database with Redis Flex enabled. 1. Connect to your new database. ## Install Redis Enterprise Software @@ -70,7 +71,7 @@ To verify the disk configuration, run: sudo lsblk ``` -## Set up a cluster and enable Auto Tiering +## Set up a cluster and enable Redis Flex 1. Direct your browser to `https://localhost:8443` on the host machine to see the Redis Enterprise Software Cluster Manager UI. @@ -111,7 +112,7 @@ On the **Databases** screen: 1. Select **Create**. -You now have a database with Auto Tiering enabled! +You now have a database with Redis Flex enabled! ## Connect to your database @@ -119,4 +120,4 @@ After you create the database, you can connect to it and store data. See [Test c ## Next steps -To see the true performance and scale of Auto Tiering, you must tune your I/O path and set the flash path to the mounted path of SSD or NVMe flash memory as that is what it is designed to run on. For more information, see [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}). +To see the true performance and scale of Redis Flex, you must tune your I/O path and set the flash path to the mounted path of SSD or NVMe flash memory as that is what it is designed to run on. For more information, see [Redis Flex and Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}). diff --git a/content/operate/rs/databases/auto-tiering/storage-engine.md b/content/operate/rs/databases/flash/storage-engine.md similarity index 94% rename from content/operate/rs/databases/auto-tiering/storage-engine.md rename to content/operate/rs/databases/flash/storage-engine.md index e859418b2e..235b790e69 100644 --- a/content/operate/rs/databases/auto-tiering/storage-engine.md +++ b/content/operate/rs/databases/flash/storage-engine.md @@ -8,16 +8,19 @@ categories: description: Manage the storage engine used for your database with auto tiering enabled. linkTitle: Manage storage engine weight: 100 +aliases: /operate/rs/databases/auto-tiering/storage-engine/ --- ## Manage the storage engine -Redis Enterprise Auto Tiering supports two storage engines: +Auto Tiering supports two storage engines: - Speedb: Redis proprietary storage engine. The default and recommended storage engine as of Redis Enterprise Software version 7.2.4. - [RocksDB](https://rocksdb.org/): Used up to Redis version 6.2. Deprecated for later Redis versions. +Redis Flex supports Speedb only. + {{}}Switching between storage engines requires guidance by Redis Support or your Account Manager.{{}} ### Change the storage engine diff --git a/content/operate/rs/databases/memory-performance/_index.md b/content/operate/rs/databases/memory-performance/_index.md index c819fc8ed5..5fe7ce9e36 100644 --- a/content/operate/rs/databases/memory-performance/_index.md +++ b/content/operate/rs/databases/memory-performance/_index.md @@ -44,9 +44,9 @@ For more info on data persistence see [Database persistence with Redis Enterpris ## Auto Tiering -By default, Redis Enterprise Software stores your data entirely in [RAM](https://en.wikipedia.org/wiki/Random-access_memory) for improved performance. The [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) feature enables your data to span both RAM and [SSD](https://en.wikipedia.org/wiki/Solid-state_drive) storage ([flash memory](https://en.wikipedia.org/wiki/Flash_memory)). Keys are always stored in RAM, but Auto Tiering manages the location of their values. Frequently used (hot) values are stored on RAM, but infrequently used (warm) values are moved to flash memory. This saves on expensive RAM space, which give you comparable performance at a lower cost for large datasets. +By default, Redis Enterprise Software stores your data entirely in [RAM](https://en.wikipedia.org/wiki/Random-access_memory) for improved performance. [Redis Flex and Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}) enable your data to span both RAM and [SSD](https://en.wikipedia.org/wiki/Solid-state_drive) storage ([flash memory](https://en.wikipedia.org/wiki/Flash_memory)). Keys are always stored in RAM, but Auto Tiering manages the location of their values. Frequently used (hot) values are stored on RAM, but infrequently used (warm) values are moved to flash memory. This saves on expensive RAM space, which give you comparable performance at a lower cost for large datasets. -For more info, see [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}). +For more info, see [Redis Flex and Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}). ## Shard placement diff --git a/content/operate/rs/databases/memory-performance/eviction-policy.md b/content/operate/rs/databases/memory-performance/eviction-policy.md index 5544422be8..111c709bff 100644 --- a/content/operate/rs/databases/memory-performance/eviction-policy.md +++ b/content/operate/rs/databases/memory-performance/eviction-policy.md @@ -52,7 +52,7 @@ Data eviction policies are not supported for Active-Active databases with Auto T To avoid data eviction, make sure your database is large enough to hold required values. -For larger databases, consider using [Auto Tiering ]({{< relref "/operate/rs/databases/auto-tiering/" >}}). +For larger databases, consider using [Redis Flex or Auto Tiering ]({{< relref "/operate/rs/databases/flash/" >}}). Auto Tiering stores actively-used data (also known as _hot data_) in RAM and the remaining data in flash memory (SSD). This lets you retain more data while ensuring the fastest access to the most critical data. diff --git a/content/operate/rs/databases/memory-performance/memory-limit.md b/content/operate/rs/databases/memory-performance/memory-limit.md index 430d487b2b..7e2e00daa4 100644 --- a/content/operate/rs/databases/memory-performance/memory-limit.md +++ b/content/operate/rs/databases/memory-performance/memory-limit.md @@ -51,8 +51,8 @@ Redis Enterprise Software protects the existing data and prevents the database You can configure the cluster to move the data to another node, or even discard it according to the [eviction policy]({{< relref "/operate/rs/databases/memory-performance/eviction-policy.md" >}}) set on each database by the administrator. -[Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) -manages memory so that you can also use flash memory (SSD) to store data. +[Redis Flex and Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}) +manage memory so that you can also use flash memory (SSD) to store data. ### Order of events for low RAM diff --git a/content/operate/rs/installing-upgrading/install/install-on-linux.md b/content/operate/rs/installing-upgrading/install/install-on-linux.md index 1db706913d..732f71cb58 100644 --- a/content/operate/rs/installing-upgrading/install/install-on-linux.md +++ b/content/operate/rs/installing-upgrading/install/install-on-linux.md @@ -96,9 +96,9 @@ To skip the installation questions, use one of the following methods: 1. Repeat this process for each node in the cluster. -## Auto Tiering installation +## Redis Flex and Auto Tiering installation -If you want to use Auto Tiering for your databases, review the prerequisites, storage requirements, and [other considerations]({{< relref "/operate/rs/databases/auto-tiering/" >}}) for Auto Tiering databases and prepare and format the flash memory. +If you want to use Redis Flex or Auto Tiering for your databases, review the prerequisites, storage requirements, and [other considerations]({{< relref "/operate/rs/databases/flash/" >}}) and prepare and format the flash memory. After you install Redis Enterprise Software, use the `prepare_flash` script to prepare and format flash memory: diff --git a/content/operate/rs/installing-upgrading/install/plan-deployment/configuring-aws-instances.md b/content/operate/rs/installing-upgrading/install/plan-deployment/configuring-aws-instances.md index 11dd3586c9..d35c9f571d 100644 --- a/content/operate/rs/installing-upgrading/install/plan-deployment/configuring-aws-instances.md +++ b/content/operate/rs/installing-upgrading/install/plan-deployment/configuring-aws-instances.md @@ -43,7 +43,7 @@ Provisioned IOPS for EBS-backed volumes. Provisioned IOPS guarantee a certain level of disk performance. There are two features in Redis Enterprise Software where this feature could be critical to use: -1. When using [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) +1. When using [Redis Flex or Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}) 1. When using AOF on every write and there is a high write load. In this case, the provisioned IOPS should be on the nodes used as replicas in the cluster. diff --git a/content/operate/rs/installing-upgrading/quickstarts/_index.md b/content/operate/rs/installing-upgrading/quickstarts/_index.md index 71f3814c32..f1643a4a42 100644 --- a/content/operate/rs/installing-upgrading/quickstarts/_index.md +++ b/content/operate/rs/installing-upgrading/quickstarts/_index.md @@ -19,7 +19,7 @@ Try out Redis Enterprise Software using one of the following quickstarts: Additional quickstart guides are available to help you: -- Set up a [Auto Tiering cluster]({{< relref "/operate/rs/databases/auto-tiering/quickstart.md" >}}) to optimize memory resources. +- Set up a [Redis Flex or Auto Tiering cluster]({{< relref "/operate/rs/databases/flash/quickstart" >}}) to optimize memory resources. - Set up an [Active-Active cluster]({{< relref "/operate/rs/databases/active-active/get-started.md" >}}) to enable high availability. diff --git a/content/operate/rs/monitoring/v1_monitoring.md b/content/operate/rs/monitoring/v1_monitoring.md index c556053468..646aa614db 100644 --- a/content/operate/rs/monitoring/v1_monitoring.md +++ b/content/operate/rs/monitoring/v1_monitoring.md @@ -94,7 +94,7 @@ We recommend that you show two similar metrics in the top graphs so you can comp See the following topics for metrics definitions: - [Database operations]({{< relref "/operate/rs/references/metrics/database-operations" >}}) for database metrics - [Resource usage]({{< relref "/operate/rs/references/metrics/resource-usage" >}}) for resource and database usage metrics -- [Auto Tiering]({{< relref "/operate/rs/references/metrics/auto-tiering" >}}) for additional metrics for [Auto Tiering ]({{< relref "/operate/rs/databases/auto-tiering" >}}) databases +- [Auto Tiering]({{< relref "/operate/rs/references/metrics/auto-tiering" >}}) for additional metrics for [Auto Tiering ]({{< relref "/operate/rs/databases/flash" >}}) databases ## Cluster alerts diff --git a/content/operate/rs/references/metrics/_index.md b/content/operate/rs/references/metrics/_index.md index cec36f39eb..173ebf938c 100644 --- a/content/operate/rs/references/metrics/_index.md +++ b/content/operate/rs/references/metrics/_index.md @@ -19,7 +19,7 @@ In the Redis Enterprise Cluster Manager UI, you can see real-time performance me See the following topics for metrics definitions: - [Database operations]({{< relref "/operate/rs/references/metrics/database-operations" >}}) for database metrics - [Resource usage]({{< relref "/operate/rs/references/metrics/resource-usage" >}}) for resource and database usage metrics -- [Auto Tiering]({{< relref "/operate/rs/references/metrics/auto-tiering" >}}) for additional metrics for [Auto Tiering ]({{< relref "/operate/rs/databases/auto-tiering" >}}) databases +- [Auto Tiering]({{< relref "/operate/rs/references/metrics/auto-tiering" >}}) for additional metrics for [Auto Tiering ]({{< relref "/operate/rs/databases/flash" >}}) databases ## Prometheus metrics diff --git a/content/operate/rs/references/metrics/auto-tiering.md b/content/operate/rs/references/metrics/auto-tiering.md index 360922e3a8..5f99520d2e 100644 --- a/content/operate/rs/references/metrics/auto-tiering.md +++ b/content/operate/rs/references/metrics/auto-tiering.md @@ -1,16 +1,16 @@ --- -Title: Auto Tiering Metrics +Title: Redis Flex and Auto Tiering Metrics alwaysopen: false categories: - docs - operate - rs description: null -linkTitle: Auto Tiering +linkTitle: Redis Flex and Auto Tiering weight: $weight --- -These metrics are additional metrics for [Auto Tiering ]({{< relref "/operate/rs/databases/auto-tiering" >}}) databases. +These metrics are additional metrics for [Redis Flex and Auto Tiering ]({{< relref "/operate/rs/databases/flash" >}}) databases. #### % Values in RAM diff --git a/content/operate/rs/references/metrics/resource-usage.md b/content/operate/rs/references/metrics/resource-usage.md index 4bb71efa1c..d60af1aa0a 100644 --- a/content/operate/rs/references/metrics/resource-usage.md +++ b/content/operate/rs/references/metrics/resource-usage.md @@ -49,7 +49,7 @@ Remaining unused disk space. ## Memory ### Used memory -Total memory used by the database, including RAM, [Flash]({{< relref "/operate/rs/databases/auto-tiering" >}}) (if enabled), and [replication]({{< relref "/operate/rs/databases/durability-ha/replication" >}}) (if enabled). +Total memory used by the database, including RAM, [Flash]({{< relref "/operate/rs/databases/flash" >}}) (if enabled), and [replication]({{< relref "/operate/rs/databases/durability-ha/replication" >}}) (if enabled). Used memory does not include: diff --git a/content/operate/rs/references/rest-api/objects/bootstrap/node_identity.md b/content/operate/rs/references/rest-api/objects/bootstrap/node_identity.md index e43ec453df..fb6c589466 100644 --- a/content/operate/rs/references/rest-api/objects/bootstrap/node_identity.md +++ b/content/operate/rs/references/rest-api/objects/bootstrap/node_identity.md @@ -14,7 +14,7 @@ weight: $weight | Name | Type/Value | Description | |------|------------|-------------| | bigstore_driver | 'rocksdb' | Bigstore driver name or none (deprecated, use the [cluster object]({{< relref "/operate/rs/references/rest-api/objects/cluster" >}})'s `bigstore_driver` instead) | -| bigstore_enabled | boolean (default: false) | If `true`, then flash storage is enabled on this node for [Auto Tiering]({{}}) databases. Configurable during [bootstrapping]({{}}). After bootstrapping, it is read-only. | +| bigstore_enabled | boolean (default: false) | If `true`, then flash storage is enabled on this node for [Redis Flex and Auto Tiering]({{}}) databases. Configurable during [bootstrapping]({{}}). After bootstrapping, it is read-only. | | identity | [identity]({{< relref "/operate/rs/references/rest-api/objects/bootstrap/identity" >}}) object | Node identity | | limits | [limits]({{< relref "/operate/rs/references/rest-api/objects/bootstrap/limits" >}}) object | Node limits | | paths | [paths]({{< relref "/operate/rs/references/rest-api/objects/bootstrap/paths" >}}) object | Storage paths object | diff --git a/content/operate/rs/references/rest-api/objects/cluster/_index.md b/content/operate/rs/references/rest-api/objects/cluster/_index.md index ee14d85228..608f6331f5 100644 --- a/content/operate/rs/references/rest-api/objects/cluster/_index.md +++ b/content/operate/rs/references/rest-api/objects/cluster/_index.md @@ -17,7 +17,7 @@ An API object that represents the cluster. |------|------------|-------------| | alert_settings | [alert_settings]({{< relref "/operate/rs/references/rest-api/objects/cluster/alert_settings" >}}) object | Cluster and node alert settings | | availability_lag_tolerance_ms | integer (default: 100) | The maximum replication lag in milliseconds tolerated between source and replicas during [lag-aware database availability checks]({{}}). | -| bigstore_driver | "speedb"
"rocksdb" | Storage engine for [Auto Tiering]({{}}) | +| bigstore_driver | "speedb"
"rocksdb" | Storage engine for [Redis Flex or Auto Tiering]({{}}) | | cluster_ssh_public_key | string | Cluster's autogenerated SSH public key | | cm_port | integer, (range: 1024-65535) | UI HTTPS listening port | | cm_session_timeout_minutes | integer (default: 15) | The timeout (in minutes) for the session to the CM | diff --git a/content/operate/rs/references/rest-api/objects/node.md b/content/operate/rs/references/rest-api/objects/node.md index 7704911a4c..98c0e5cf9b 100644 --- a/content/operate/rs/references/rest-api/objects/node.md +++ b/content/operate/rs/references/rest-api/objects/node.md @@ -20,7 +20,7 @@ An API object that represents a node in the cluster. | architecture | string | Hardware architecture (read-only) | | bigredis_storage_path | string | Flash storage path (read-only) | | bigstore_driver | 'ibm-capi-ga1'
'ibm-capi-ga2'
'ibm-capi-ga4'
'speedb'
'rocksdb' | Bigstore driver name or none (deprecated as of Redis Enterprise v7.2, use the [cluster object]({{< relref "/operate/rs/references/rest-api/objects/cluster" >}})'s `bigstore_driver` instead) | -| bigstore_enabled | boolean | If `true`, then flash storage is enabled on this node for [Auto Tiering]({{}}) databases. Configurable during [bootstrapping]({{}}). After bootstrapping, it is read-only. | +| bigstore_enabled | boolean | If `true`, then flash storage is enabled on this node for [Redis Flex and Auto Tiering]({{}}) databases. Configurable during [bootstrapping]({{}}). After bootstrapping, it is read-only. | | bigstore_size | integer | Storage size of bigstore storage (read-only) | | cores | integer | Total number of CPU cores (read-only) | | ephemeral_storage_path | string | Ephemeral storage path (read-only) | diff --git a/content/operate/rs/release-notes/legacy-release-notes/rlec-4-3-aug-2016.md b/content/operate/rs/release-notes/legacy-release-notes/rlec-4-3-aug-2016.md index 84dd2f08a3..3f98d82b5d 100644 --- a/content/operate/rs/release-notes/legacy-release-notes/rlec-4-3-aug-2016.md +++ b/content/operate/rs/release-notes/legacy-release-notes/rlec-4-3-aug-2016.md @@ -23,7 +23,7 @@ upgrade to this version. - Various improvements to internal performance and stability were implemented. - RLEC Flash functionality added. For additional details, refer to - [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) + [Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}) and contact if you are interested in this functionality. - Support for Redis version 3.0 added. When you install or upgrade the diff --git a/content/operate/rs/release-notes/legacy-release-notes/rs-5-6-0-april-2020.md b/content/operate/rs/release-notes/legacy-release-notes/rs-5-6-0-april-2020.md index a792f448e2..131afaa50b 100644 --- a/content/operate/rs/release-notes/legacy-release-notes/rs-5-6-0-april-2020.md +++ b/content/operate/rs/release-notes/legacy-release-notes/rs-5-6-0-april-2020.md @@ -62,7 +62,7 @@ For more information, check out the [HyperLogLog on Active-Active documentation] ### RedisJSON on Auto Tiering -RS 5.6.0 adds support for [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) databases with [Redis Modules](https://docs.redis.com/latest/modules). [RedisJSON]({{< relref "/operate/oss_and_stack/stack-with-enterprise/json" >}}) is the first module to be available to run on a database with Auto Tiering enabled. +RS 5.6.0 adds support for [Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}) databases with [Redis Modules](https://docs.redis.com/latest/modules). [RedisJSON]({{< relref "/operate/oss_and_stack/stack-with-enterprise/json" >}}) is the first module to be available to run on a database with Auto Tiering enabled. Using RedisJSON on Auto Tiering allows you to benefit from high performance redis with high data volume at lower costs. diff --git a/content/operate/rs/release-notes/rs-7-2-4-releases/rs-7-2-4-52.md b/content/operate/rs/release-notes/rs-7-2-4-releases/rs-7-2-4-52.md index ba54f4b515..8f1816b857 100644 --- a/content/operate/rs/release-notes/rs-7-2-4-releases/rs-7-2-4-52.md +++ b/content/operate/rs/release-notes/rs-7-2-4-releases/rs-7-2-4-52.md @@ -103,9 +103,9 @@ To switch existing databases to use Speedb for Auto Tiering and improve performa For more information about Auto Tiering, see: -- [Auto Tiering overview]({{< relref "/operate/rs/databases/auto-tiering" >}}) +- [Auto Tiering overview]({{< relref "/operate/rs/databases/flash" >}}) -- [Auto Tiering quick start]({{< relref "/operate/rs/databases/auto-tiering/quickstart" >}}) +- [Auto Tiering quick start]({{< relref "/operate/rs/databases/flash/quickstart" >}}) #### RESP3 support