All Products
Search
Document Center

Tair (Redis® OSS-Compatible):Discontinuation of new purchases for Tair (Enterprise Edition) Persistent Memory instances

Last Updated:Apr 23, 2026

Due to supply chain constraints for persistent memory hardware, we will discontinue new purchases of all Tair (Enterprise Edition) Persistent Memory instance types effective May 30, 2026. We are introducing the Persistence-enhanced instance type as a comprehensive replacement. This new product, built on the Tair Memory-based Edition core, matches the features and performance of Persistent Memory instances and has an ample supply. Your existing Persistent Memory instances can continue to operate, but we may not be able to fulfill future scale-up requests. We recommend planning your migration as soon as possible.

Phase-out timeline

Date

Description

May 30, 2026

We will disable the purchase option for all Persistent Memory instance types. After this date, no customers will be able to make new purchases.

Impact of the phase-out

Customer type

Impact

Customers with existing Persistent Memory instances

  • Renewal: This change does not affect renewals for your existing Persistent Memory instances.

  • Scale-up: The success of a scale-up operation depends on resource availability in the instance's availability zone. Therefore, we recommend migrating existing instances as soon as possible.

Customers planning to purchase new Persistent Memory instances

You will no longer be able to select the Persistent Memory instance type when you create an instance. Please select the Persistence-enhanced type instead.

New purchases: Persistence-enhanced

For new purchases, we recommend the Tair Persistence-enhanced instance type:

  • It is built on the Tair Memory-based Edition and offers complete feature parity with the Persistent Memory type.

  • It delivers the same performance as the original Persistent Memory instances at a similar price.

  • We maintain an ample supply to support on-demand scale-ups.

Note

The Persistence-enhanced instance type is currently in a limited-access phase. To purchase this instance type, please submit a ticket to request access.

Purchase guide

Purchase in the console

  1. Submit a ticket to request purchase access for Persistence-enhanced instances.

  2. After access is granted, go to the Tair purchase page and set Product to Tair (Enterprise Edition).

  3. Set Storage Type to Memory.

  4. For Shard Specification, select an xx GB (Persistence-enhanced) instance type. This option is visible only after purchase access is granted.

  5. Configure other settings as needed, such as region, network type, and instance architecture. The rest of the process is the same as for other Tair products.

Purchase using API

To purchase an instance by using OpenAPI, call the Create a Tair (Enterprise Edition) instance operation and set the InstanceClass parameter to an instance class listed in the tables below.

Important
  • Unlike when creating Persistent Memory instances, you must set the InstanceType parameter to tair_rdb and the EngineVersion parameter to a supported version, such as 5.0, 6.0, or 7.0.

  • Other parameters such as region, network, and instance architecture are the same as those for Tair Memory-based Edition instances.

  • The ESSD cloud disk is used for temporary storage of non-data content such as logs and backups. Your data is stored in memory.

Cluster Edition (Proxy), Cluster Edition (Read/Write Splitting), or Standard Edition (Read/Write Splitting) architectures:

Instance type

Instance class (InstanceClass)

vCPU

Memory (GB)

ESSD cloud disk (GB)

Bandwidth

Max connections

QPS (reference)

4 GB (Persistence-enhanced)

tair.rdb.with.proxy.4g.2io

2

4

20

768 Mbps (96 MB/s)

20,000

100,000

8 GB (Persistence-enhanced)

tair.rdb.with.proxy.8g.2io

2

8

40

768 Mbps (96 MB/s)

20,000

100,000

16 GB (Persistence-enhanced)

tair.rdb.with.proxy.16g.2io

2

16

80

768 Mbps (96 MB/s)

20,000

100,000

32 GB (Persistence-enhanced)

tair.rdb.with.proxy.32g.2io

2

32

160

768 Mbps (96 MB/s)

30,000

100,000

64 GB (Persistence-enhanced)

tair.rdb.with.proxy.64g.2io

2

64

320

768 Mbps (96 MB/s)

30,000

100,000

Cluster Edition (Direct Connection) or Standard Edition architectures:

Instance type

Instance class (InstanceClass)

vCPU

Memory (GB)

ESSD cloud disk (GB)

Bandwidth

Max connections

QPS (reference)

4 GB (Persistence-enhanced)

tair.rdb.4g.2io

2

4

20

768 Mbps (96 MB/s)

20,000

100,000

8 GB (Persistence-enhanced)

tair.rdb.8g.2io

2

8

40

768 Mbps (96 MB/s)

20,000

100,000

16 GB (Persistence-enhanced)

tair.rdb.16g.2io

2

16

80

768 Mbps (96 MB/s)

20,000

100,000

32 GB (Persistence-enhanced)

tair.rdb.32g.2io

2

32

160

768 Mbps (96 MB/s)

30,000

100,000

64 GB (Persistence-enhanced)

tair.rdb.64g.2io

2

64

320

768 Mbps (96 MB/s)

30,000

100,000

Migrating existing instances

We recommend using Data Transmission Service (DTS) to seamlessly migrate your existing Persistent Memory instances to Persistence-enhanced instances without service downtime:

  1. Request access to and purchase a target Persistence-enhanced instance. The target instance must have specifications equal to or greater than the source instance.

  2. Follow the guide for one-way migration between instances to migrate your data and then verify data consistency.

  3. During off-peak hours, switch your application's connection endpoint to the target instance.

  4. After ensuring stable operation, release the source instance and the DTS synchronization task.

Monitoring and alerting

After migrating to or purchasing a Tair Persistence-enhanced instance, update your monitoring and alert configurations to reflect the following changes:

  • Metric changes: You no longer need to monitor the Persistent Memory-related metrics Tair_PmemUsage and Tair_Pmem. Instead, monitor the standard memory metrics MemoryUsage and UsedMemory.

  • CloudMonitor alert settings: When you create an alert rule in CloudMonitor, select the Tair Memory-based Edition product and its corresponding metrics.

FAQ

  • Q: Will my existing Persistent Memory instances be forcibly phased out after new purchases are discontinued?

    A: No. This change only disables the option for new purchases. Your existing Persistent Memory instances can continue to run normally and support renewals and specification changes. They will not be forcibly phased out or migrated.

  • Q: Are there any differences in features or performance between the Persistence-enhanced and Persistent Memory types?

    A: The Persistence-enhanced type is customized and optimized based on the Tair Memory-based Edition and matches the features and performance of the original Persistent Memory type at a similar price. Migrating from a Persistent Memory instance to a Persistence-enhanced instance will not affect business compatibility.

  • Q: Why are new purchases for Persistent Memory instances being discontinued?

    A: The supply chain for the underlying persistent memory hardware is constrained, which prevents us from guaranteeing availability for new purchases and large-scale scale-ups. We have introduced the Persistence-enhanced instance type as a comprehensive replacement.

  • Q: Will the ability to scale up my existing instances be affected?

    A: Yes. Due to hardware supply limitations, scaling up an existing instance depends on the resource availability in its availability zone. If you anticipate business growth, we recommend migrating to a Persistence-enhanced instance by using DTS as soon as possible.

  • Q: How do I request to purchase a Persistence-enhanced instance?

    A: The Persistence-enhanced instance type is currently in a limited-access phase. Please submit a ticket to request access.