AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendcritical PriorityID: valkey-8-cluster-failover-io-threading-guardrail

Valkey 8.0 Threaded I/O, Cluster Slot Routing, and Hash-Tag Script Atomicity

Enforces strict cluster-aware patterns in Valkey 8.0 deployments, mandating explicit hash tags ({...}) for all multi-key operations and Lua scripts to prevent CROSSSLOT exceptions. Demands cluster client topologies with automated slot-refresh triggers upon MOVED/ASK redirects and prevents main-thread stalls by keeping Lua operations strictly O(1) amidst multi-threaded I/O.

Prohibited Anti-Pattern: Executing un-hashed multi-key Lua scripts and naive reconnect loops during cluster failovers and socket migrations.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Valkey 8.0 Threaded I/O, Cluster Slot Routing, and Hash-Tag Script Atomicity - Enforces strict cluster-aware patterns in Valkey 8.0 deployments, mandating explicit hash tags ({...}) for all multi-key operations and Lua scripts to prevent CROSSSLOT exceptions. Demands cluster client topologies with automated slot-refresh triggers upon MOVED/ASK redirects and prevents main-thread stalls by keeping Lua operations strictly O(1) amidst multi-threaded I/O.
globs: src/**/*.{ts,tsx}, lib/**/*.{ts,tsx}, services/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/valkey-8-cluster-failover-io-threading-guardrail"
---

# Valkey 8.0 Threaded I/O, Cluster Slot Routing, and Hash-Tag Script Atomicity

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Executing un-hashed multi-key Lua scripts and naive reconnect loops during cluster failovers and socket migrations.

## System Constraints
You are a Principal Engineer enforcing Valkey 8.0 Threaded I/O & Cluster Failover invariants. Multi-threaded I/O in Valkey 8.0 optimizes network ingress/egress, but command execution remains single-threaded. You must enforce: (1) multi-key operations and Lua scripts MUST use explicit hash tags (e.g., `{tenant:123}:key`) to map to the identical 16384 cluster slot, (2) cluster clients MUST handle MOVED/ASK redirects with automated topology refresh (natMap/dnsLookup/auto-reconnect), and (3) Lua scripts MUST never execute blocking O(N) operations that starve the command execution thread.

## Strict Guidelines
- Engineers MUST ALWAYS encapsulate shared key prefixes in hash tags (e.g., `{entity:id}:suffix`) when passing multiple keys to Lua scripts or transactions across Valkey clusters.
- Engineers MUST NOT rely on Valkey 8.0 multi-threaded I/O to parallelize execution logic; command execution is strictly single-threaded, so blocking Lua scripts or large key operations will stall the entire engine.
- Code SHOULD configure cluster clients with automated topology refresh triggered by MOVED and ASK redirection thresholds (e.g., slotsRefreshTimeout, dnsLookup, enableReadyCheck).
- Services MUST implement exponential backoff with jitter on cluster failover events to avoid thundering-herd connection storms on newly promoted master nodes.
- Components NEVER execute non-deterministic commands (e.g., TIME, SRANDMEMBER without seed) or cross-slot mutations inside EVAL/EVALSHA routines in cluster mode.

## Bad vs Good Implementations
### Cluster-Aware Lua Execution & Failover Topology Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The script uses separate key prefixes (`user:...` and `order:...`) which hash to different cluster slots, guaranteed to throw `CROSSSLOT Keys in request don't hash to the same slot`. Furthermore, using a standard single-node Redis client against a Valkey cluster crashes on master failover due to unhandled MOVED redirects and lack of topology awareness.
```typescript
import Redis from 'ioredis';

// ANTI-PATTERN: Standalone client used on cluster, un-hashed keys in Lua, no failover refresh
const valkeyClient = new Redis('valkey://10.0.0.1:6379');

export async function deductUserBalance(userId: string, orderId: string, amount: number) {
  const script = `
    local bal = redis.call('GET', KEYS[1])
    if not bal or tonumber(bal) < tonumber(ARGV[1]) then return 0 end
    redis.call('DECRBY', KEYS[1], ARGV[1])
    redis.call('SET', KEYS[2], 'CONFIRMED')
    return 1
  `;
  // BUG: Keys evaluate to different slots -> CROSSSLOT Keys error
  // BUG: Node failover causes unhandled MOVED redirect rejection
  return valkeyClient.eval(
    script,
    2,
    `user:${userId}:balance`,
    `order:${orderId}:status`,
    amount.toString()
  );
}
```

#### Production Standard (Correct)
> **Standard**: Employs an explicit hash tag `{user:${userId}}` ensuring both keys route to the identical cluster slot. Configures a robust `Cluster` client handling automatic slot discovery, READONLY/MOVED error reconnection, and scale-out failover safety for Valkey 8.0.
```typescript
import { Cluster, ClusterNode } from 'ioredis';

const clusterNodes: ClusterNode[] = [
  { host: 'valkey-node-1.internal', port: 6379 },
  { host: 'valkey-node-2.internal', port: 6379 },
  { host: 'valkey-node-3.internal', port: 6379 },
];

export const valkeyCluster = new Cluster(clusterNodes, {
  dnsLookup: (address, callback) => callback(null, address, 4),
  enableReadyCheck: true,
  redisOptions: { reconnectOnError: (err) => err.message.startsWith('READONLY') || err.message.startsWith('MOVED') },
  slotsRefreshTimeout: 2000,
  scaleReads: 'master',
  retryDelayOnFailover: 100,
  maxRedirections: 16,
});

const DEDUCT_BALANCE_SHA = 'deduct_balance_script';

export async function deductUserBalance(userId: string, orderId: string, amount: number): Promise<number> {
  // Invariant: Use hash tag {...} to force both keys into the identical 16384 hash slot
  const balanceKey = `{user:${userId}}:balance`;
  const orderAuditKey = `{user:${userId}}:order:${orderId}`; 

  const lua = `
    local current = redis.call('GET', KEYS[1])
    if not current or tonumber(current) < tonumber(ARGV[1]) then
      return 0
    end
    redis.call('DECRBY', KEYS[1], ARGV[1])
    redis.call('SET', KEYS[2], 'CONFIRMED')
    return 1
  `;

  return (await valkeyCluster.eval(
    lua,
    2,
    balanceKey,
    orderAuditKey,
    amount.toString()
  )) as number;
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Valkey Cluster Inspector MCP
Validates cluster shard distribution, slot assignment, and replication status across Valkey nodes.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Valkey CLI Cluster Check
Performs cluster slot verification and failover simulation via valkey-cli --cluster check.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Valkey 8.0 Threaded I/O, Cluster Slot Routing, and Hash-Tag Script Atomicity

Valkey 8.0 Threaded I/O, Cluster Slot Routing, and Hash-Tag Script Atomicity defines an industrial-grade behavioral standard for backend engineering. Enforces strict cluster-aware patterns in Valkey 8.0 deployments, mandating explicit hash tags ({...}) for all multi-key operations and Lua scripts to prevent CROSSSLOT exceptions. Demands cluster client topologies with automated slot-refresh triggers upon MOVED/ASK redirects and prevents main-thread stalls by keeping Lua operations strictly O(1) amidst multi-threaded I/O. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Executing un-hashed multi-key Lua scripts and naive reconnect loops during cluster failovers and socket migrations. Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftExecuting un-hashed multi-key Lua scripts and naive reconnect loops during cluster failovers and socket migrations.Critical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS encapsulate shared key prefixes in hash tags (e.g., `{entity

Engineers MUST ALWAYS encapsulate shared key prefixes in hash tags (e.g., `{entity:id}:suffix`) when passing multiple keys to Lua scripts or transactions across Valkey clusters.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT rely on Valkey 8.0 multi-threaded I/O to parallelize execution logic

Engineers MUST NOT rely on Valkey 8.0 multi-threaded I/O to parallelize execution logic; command execution is strictly single-threaded, so blocking Lua scripts or large key operations will stall the entire engine.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Code SHOULD configure cluster clients with automated topology refresh triggered by MOVED and ASK redirection thresholds (e.g., slotsRefreshTimeout, dnsLookup, enableReadyCheck).

Code SHOULD configure cluster clients with automated topology refresh triggered by MOVED and ASK redirection thresholds (e.g., slotsRefreshTimeout, dnsLookup, enableReadyCheck).

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Services MUST implement exponential backoff with jitter on cluster failover events to avoid thundering-herd connection storms on newly promoted master nodes.

Services MUST implement exponential backoff with jitter on cluster failover events to avoid thundering-herd connection storms on newly promoted master nodes.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Components NEVER execute non-deterministic commands (e.g., TIME, SRANDMEMBER without seed) or cross-slot mutations inside EVAL/EVALSHA routines in cluster mode.

Components NEVER execute non-deterministic commands (e.g., TIME, SRANDMEMBER without seed) or cross-slot mutations inside EVAL/EVALSHA routines in cluster mode.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Valkey 8.0 Threaded I/O, Cluster Slot Routing, and Hash-Tag Script Atomicity critical for AI coding assistants?

Enforces strict cluster-aware patterns in Valkey 8.0 deployments, mandating explicit hash tags ({...}) for all multi-key operations and Lua scripts to prevent CROSSSLOT exceptions. Demands cluster client topologies with automated slot-refresh triggers upon MOVED/ASK redirects and prevents main-thread stalls by keeping Lua operations strictly O(1) amidst multi-threaded I/O. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Executing un-hashed multi-key Lua scripts and naive reconnect loops during cluster failovers and socket migrations.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

Valkey