diff --git a/content/develop/clients/failover.md b/content/develop/clients/failover.md index 613157b5bf..cc130559bf 100644 --- a/content/develop/clients/failover.md +++ b/content/develop/clients/failover.md @@ -40,7 +40,7 @@ along with their release state and available features. | :-- | :-- | :-- | :-- | :-- | | [Jedis](/content/develop/clients/jedis/failover.md) | Yes | No | No | Yes | | [redis-py](/content/develop/clients/redis-py/failover.md) | Yes (Preview) | Yes | Yes | Yes | -| [Lettuce](/content/develop/clients/lettuce/failover.md) | Yes (Preview) | Yes | No | Yes | +| [Lettuce](/content/develop/clients/lettuce/failover.md) | Yes | Yes | No | Yes | | [StackExchange.Redis](/content/develop/clients/dotnet/failover.md) | Yes | Yes | Yes | Yes | ## Concepts diff --git a/content/develop/clients/go/connect.md b/content/develop/clients/go/connect.md index 158c52df25..4be1b8e1e5 100644 --- a/content/develop/clients/go/connect.md +++ b/content/develop/clients/go/connect.md @@ -221,11 +221,11 @@ The `maintnotifications.Config` object accepts the following parameters: | `MaxHandoffRetries` | The maximum number of times to retry connecting to the replacement node. The default is 3. | > [!NOTE] -> Redis Cloud supports relaxed timeouts *only* (and not pre-handoffs) for SCH if you are using -> either [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) or +> Redis Cloud supports relaxed timeouts *only* (and not pre-handoffs) for SCH if you are using > [Google Cloud Private Service Connect](/content/operate/rc/security/private-service-connect.md) +> or the OSS Cluster API with [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) > (see [Smart client handoffs](/content/develop/clients/sch.md#redis-cloud) for more information). -> To use relaxed timeouts with these services, you should set `EndpointType: maintnotifications.EndpointTypeNone` +> To use relaxed timeouts with these connections, you should set `EndpointType: maintnotifications.EndpointTypeNone` > when you connect. All other configurations have full support for both relaxed timeouts and pre-handoffs. ## Connect using client-side caching diff --git a/content/develop/clients/lettuce/connect.md b/content/develop/clients/lettuce/connect.md index e5f43f64b6..4304151eee 100644 --- a/content/develop/clients/lettuce/connect.md +++ b/content/develop/clients/lettuce/connect.md @@ -431,8 +431,8 @@ that is relevant to SCH: > [!NOTE] > Redis Cloud supports relaxed timeouts *only* (and not pre-handoffs) for SCH if you are using -> either [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) or > [Google Cloud Private Service Connect](/content/operate/rc/security/private-service-connect.md) +> or the OSS Cluster API with [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) > (see [Smart client handoffs](/content/develop/clients/sch.md#redis-cloud) for more information). -> To use relaxed timeouts with these services, you should set `endpointType(EndpointType.NONE)` +> To use relaxed timeouts with these connections, you should set `endpointType(EndpointType.NONE)` > when you connect. All other configurations have full support for both relaxed timeouts and pre-handoffs. diff --git a/content/develop/clients/lettuce/failover.md b/content/develop/clients/lettuce/failover.md index de9da065e4..e4205d1b61 100644 --- a/content/develop/clients/lettuce/failover.md +++ b/content/develop/clients/lettuce/failover.md @@ -22,7 +22,6 @@ relatedPages: - /develop/clients/failover scope: [client-specific, implementation] weight: 50 -bannerText: This feature is currently in preview and may be subject to change. --- Lettuce supports [Client-side geographic failover](https://en.wikipedia.org/wiki/Failover) diff --git a/content/develop/clients/nodejs/connect.md b/content/develop/clients/nodejs/connect.md index 2ee36450ce..8f71cef1b3 100644 --- a/content/develop/clients/nodejs/connect.md +++ b/content/develop/clients/nodejs/connect.md @@ -459,11 +459,11 @@ The available options are: performing maintenance. The default is 10000 (10 seconds). If a timeout happens during the maintenance period, the client receives a `SocketTimeoutDuringMaintenance` error. > [!NOTE] -> Redis Cloud supports relaxed timeouts *only* (and not pre-handoffs) for SCH if you are using -> either [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) or +> Redis Cloud supports relaxed timeouts *only* (and not pre-handoffs) for SCH if you are using > [Google Cloud Private Service Connect](/content/operate/rc/security/private-service-connect.md) +> or the OSS Cluster API with [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) > (see [Smart client handoffs](/content/develop/clients/sch.md#redis-cloud) for more information). -> To use relaxed timeouts with these services, you should set `maintEndpointType: 'none'` +> To use relaxed timeouts with these connections, you should set `maintEndpointType: 'none'` > when you connect. All other configurations have full support for both relaxed timeouts and pre-handoffs. ## Connection events diff --git a/content/develop/clients/redis-py/connect.md b/content/develop/clients/redis-py/connect.md index 9bdf000f5f..8278bf9c63 100644 --- a/content/develop/clients/redis-py/connect.md +++ b/content/develop/clients/redis-py/connect.md @@ -374,8 +374,8 @@ The `MaintNotificationsConfig` constructor accepts the following parameters: > [!NOTE] > Redis Cloud supports relaxed timeouts *only* (and not pre-handoffs) for SCH if you are using -> either [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) or > [Google Cloud Private Service Connect](/content/operate/rc/security/private-service-connect.md) +> or the OSS Cluster API with [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) > (see [Smart client handoffs](/content/develop/clients/sch.md#redis-cloud) for more information). -> To use relaxed timeouts with these services, you should set `endpoint_type=EndpointType.NONE` +> To use relaxed timeouts with these connections, you should set `endpoint_type=EndpointType.NONE` > when you connect. All other configurations have full support for both relaxed timeouts and pre-handoffs. diff --git a/content/develop/clients/sch.md b/content/develop/clients/sch.md index e14cd7955e..49db59c93b 100644 --- a/content/develop/clients/sch.md +++ b/content/develop/clients/sch.md @@ -85,15 +85,19 @@ Standard routing covers any connection that doesn't use the OSS Cluster API. ### Redis Cloud -SCH is fully supported and enabled by default on Redis Cloud, except when you -are using one of the following options: +SCH is enabled by default on Redis Cloud. The level of support depends on how +you connect to the database and whether you use standard routing or the +[OSS Cluster API](/content/operate/rs/databases/configure/oss-cluster-api.md): -- [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) -- [Google Cloud Private Service Connect](/content/operate/rc/security/private-service-connect.md) +| Connection method | Standard routing | OSS Cluster API | +| :-- | :-- | :-- | +| [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) | Relaxed timeouts and pre-handoffs | Relaxed timeouts only | +| [Google Cloud Private Service Connect](/content/operate/rc/security/private-service-connect.md) | Relaxed timeouts only | Not available | +| All other connection methods | Relaxed timeouts and pre-handoffs | Relaxed timeouts and pre-handoffs | -These services don't currently allow for pre-handoffs, but you still get the -benefit of relaxed timeouts during database version upgrades. All other -configurations have full support for both relaxed timeouts and pre-handoffs. +"Relaxed timeouts only" means that you still get the benefit of relaxed +timeouts during database version upgrades, but the connection doesn't support +pre-handoffs. Private Service Connect doesn't support the OSS Cluster API. ### Redis Software