Tair (Redis® OSS-Compatible):Manage direct connection endpoints

Prerequisites

Before you begin, make sure your instance meets all of the following requirements.

• Use the cluster architecture with Deployment Mode set to Classic

For a cloud-native cluster instance already in direct connection mode, a direct connection endpoint is provided by default and does not need to be enabled. Cloud-native cluster architecture in proxy mode does not support enabling direct connection mode.

To enable direct connection, also ensure:

• The instance is compatible with Redis 5.0 and updated to the latest minor version

• Transport Layer Security (TLS) is disabled — see TLS encryption

• The vSwitch has enough available IP addresses: direct connection allocates one IP address to the primary node of each shard, plus one for the endpoint itself. For an 8-shard instance, the vSwitch needs at least 9 available IP addresses. To check, see Query the number of available IP addresses for the vSwitch of an instance

To release the private endpoint, also ensure:

• Direct connection mode is already enabled on the instance.

• Your application has been updated to use a different endpoint, such as the internal endpoint in proxy mode. See View endpoints

Limitations

• Reduced per-shard connections: Because the proxy is bypassed, the maximum number of connections per shard drops to 10,000 (Redis Open-Source Edition cluster) or 30,000 (Tair (Enterprise Edition) cluster). If data skew occurs — where one shard is heavily accessed while others are mostly idle — connections to that shard may be exhausted, causing new connection requests to fail. To diagnose data skew caused by hot spot keys or large keys, see Top Key statistics and Offline full key analysis.

• Major version upgrades and zone changes blocked: After enabling direct connection mode, you cannot upgrade the major version or change the zone of the instance. Release the private endpoint first, then perform the upgrade or zone change. See Upgrade the major version and Migrate an instance across zones.

• Configuration changes limited: When changing the configuration of an instance with direct connection enabled, change only the number of shards or shard specifications, and only one at a time. See Why am I unable to change the configurations of a classic (local disk-based) cluster instance?

Enable direct connection

By default, a Tair (Redis OSS-compatible) instance using the classic cluster architecture connects through a database proxy endpoint. To make the instance compatible with the native Redis Cluster protocol, enable direct connection mode and use the direct connection endpoint from your client. This lets your client bypass the proxy node and access backend data nodes directly, reducing latency by eliminating proxy request processing.

Release a private endpoint

Release the private endpoint of an ApsaraDB for Redis instance to disable direct connection mode. This is required before certain operations that direct connection mode does not support, such as changing instance configurations or upgrading a major version.

FAQ

I meet all the prerequisites, but I cannot find the Apply for Endpoint button. What should I do?

Update the instance to the latest minor version. See Update the minor version and proxy version.

Can I use the direct connection endpoint and the proxy endpoint at the same time?

For a classic cluster architecture, yes — both modes can be active simultaneously. For a cloud-native cluster architecture, only one mode can be active at a time.

API reference