Skip to content

Conversation

bsbodden
Copy link
Contributor

…ide (#72)

Fixes #72 - Document proper client configuration for Azure Cache for Redis and Redis Enterprise deployments that use proxy layers.

Changes:

  • Add comprehensive Azure/Enterprise configuration section to README
  • Add test demonstrating correct client configuration approach
  • Clarify that standard Redis client should be used, not RedisCluster
  • Explain proxy architecture and why it requires this configuration

The key is that Azure Cache for Redis and similar enterprise deployments use a proxy layer that makes clusters appear as single endpoints. This requires using a standard Redis client rather than a cluster-aware client to avoid detection issues and cross-slot errors.

…ide (#72)

Fixes #72 - Document proper client configuration for Azure Cache for Redis
and Redis Enterprise deployments that use proxy layers.

Changes:
- Add comprehensive Azure/Enterprise configuration section to README
- Add test demonstrating correct client configuration approach
- Clarify that standard Redis client should be used, not RedisCluster
- Explain proxy architecture and why it requires this configuration

The key is that Azure Cache for Redis and similar enterprise
deployments use a proxy layer that makes clusters appear as single
endpoints. This requires using a standard Redis client rather than
a cluster-aware client to avoid detection issues and cross-slot errors.
@bsbodden bsbodden self-assigned this Aug 15, 2025
Copy link
Contributor

@tylerhutcherson tylerhutcherson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. Do we need to improve documentation on the cluster_mode flag and usage for the internals of the checkpointer client?

@bsbodden bsbodden merged commit 48396d0 into main Aug 15, 2025
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue with enterprise proxy API and using standard client class
2 participants