Skip to content

Reject RedisCluster clients with a clear error#23

Merged
lesnik512 merged 1 commit intomainfrom
reject-redis-cluster-client
May 4, 2026
Merged

Reject RedisCluster clients with a clear error#23
lesnik512 merged 1 commit intomainfrom
reject-redis-cluster-client

Conversation

@lesnik512
Copy link
Copy Markdown
Member

Raises TypeError at TimersBroker construction when handed a RedisCluster client. The default key layout uses two keys per topic without a hash tag, so multi-key Lua scripts and pipelines would fail with CROSSSLOT in Cluster mode. Surfacing the limitation up front is far easier to diagnose than a later runtime CROSSSLOT from inside a Lua eval. Single-primary Redis (including Sentinel) is unchanged.

Raises TypeError at TimersBroker construction when handed a RedisCluster
client. The default key layout uses two keys per topic without a hash
tag, so multi-key Lua scripts and pipelines would fail with CROSSSLOT in
Cluster mode. Surfacing the limitation up front is far easier to
diagnose than a later runtime CROSSSLOT from inside a Lua eval.
Single-primary Redis (including Sentinel) is unchanged.
@lesnik512 lesnik512 self-assigned this May 4, 2026
@lesnik512 lesnik512 merged commit 8fe154c into main May 4, 2026
3 checks passed
@lesnik512 lesnik512 deleted the reject-redis-cluster-client branch May 4, 2026 13:27
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.

1 participant