Skip to content

DOC-7188 Add a Redis Cloud SCH support table for PrivateLink and PSC #4493

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
andy-stark-redis wants to merge 2 commits into
base: main
Choose a base branch
from
Open

DOC-7188 Add a Redis Cloud SCH support table for PrivateLink and PSC #4493

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c3ce829
DOC-7188 Add a Redis Cloud SCH support table for PrivateLink and PSC
andy-stark-redis Nov 6, 2026
d6ce40a
Tag on minor fix about Lettuce failover no longer in preview
andy-stark-redis Nov 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/develop/clients/failover.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
6 changes: 3 additions & 3 deletions content/develop/clients/go/connect.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions content/develop/clients/lettuce/connect.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
1 change: 0 additions & 1 deletion content/develop/clients/lettuce/failover.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down
6 changes: 3 additions & 3 deletions content/develop/clients/nodejs/connect.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions content/develop/clients/redis-py/connect.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
18 changes: 11 additions & 7 deletions content/develop/clients/sch.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading