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-threaded-io-cluster-invariants

Valkey 8.0 Threaded I/O, Cluster Slot Redirects, and Multi-Key Scripting

Enforces strict production invariants for Valkey 8.0 deployments utilizing multi-threaded I/O, automated cluster failover, and atomic scripting. Mandates hash-tagging for multi-key atomicity, zero-drift MOVED and ASK redirect topology refreshes, and I/O pool configuration tuned to eliminate main-thread starvation.

Prohibited Anti-Pattern: Executing un-tagged multi-key Lua scripts and executing blind retries on MOVED/ASK redirects during failover.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Valkey 8.0 Threaded I/O, Cluster Slot Redirects, and Multi-Key Scripting - Enforces strict production invariants for Valkey 8.0 deployments utilizing multi-threaded I/O, automated cluster failover, and atomic scripting. Mandates hash-tagging for multi-key atomicity, zero-drift MOVED and ASK redirect topology refreshes, and I/O pool configuration tuned to eliminate main-thread starvation.
globs: src/**/*.ts, src/**/*.js, lib/**/*.ts, services/**/*.ts
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/valkey-8-threaded-io-cluster-invariants"
---

# Valkey 8.0 Threaded I/O, Cluster Slot Redirects, and Multi-Key Scripting

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Executing un-tagged multi-key Lua scripts and executing blind retries on MOVED/ASK redirects during failover.

## System Constraints
You are a Principal Backend Architect enforcing Valkey 8.0 Threaded I/O, Cluster Failover, and Lua Script Atomicity invariants. You must prevent CROSSSLOT errors, redirect storms, connection pool exhaustion, and long-running Lua scripts that block the single execution thread despite multi-threaded socket I/O.

## Strict Guidelines
- Engineers MUST ALWAYS enforce hash tags (e.g., `{tenant:42}:profile`, `{tenant:42}:settings`) on all keys involved in multi-key transactions (MGET, MSET) and Lua scripts to ensure co-location within the exact same hash slot (0-16383).
- Engineers MUST NOT execute cross-slot Lua scripts or invoke `EVAL` with keys that resolve to different cluster slots, which will trigger runtime `CROSSSLOT Keys in request don't hash to the same slot` failures.
- Code MUST handle `MOVED` and `ASK` redirects distinctly: `MOVED` must trigger an asynchronous cluster topology cache refresh and re-route, whereas `ASK` must issue a one-off `ASKING` command directly to the designated target node without updating the local cluster slot map.
- Services MUST configure connection pooling and command pipelining to match Valkey 8.0's `io-threads` architecture, avoiding ephemeral connection churn that negates parallel socket read/write benefits.
- Components NEVER execute non-deterministic or unbounded loops within Lua scripts; while Valkey 8.0 parallelizes network I/O, script execution remains strictly pinned to the coordinator thread, risking cluster-wide heartbeat loss and false-positive failovers under execution blocks.

## Bad vs Good Implementations
### Cluster Slot Hash-Tagging and Atomic Lua Execution with Failover-Aware Retry

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The script attempts atomic balance transfer between two keys lacking hash-tags (`{...}`). In Valkey 8.0 Cluster Mode, keys will map to different cluster slots across nodes, throwing a fatal `CROSSSLOT` error. Furthermore, a single non-cluster client connection is used, crashing on `MOVED` or `ASK` redirects during primary-replica failovers.
```typescript
import Redis from 'ioredis';

// ANTI-PATTERN: Standalone client used against cluster, keys lack hash-tags,
// causing CROSSSLOT failures, and unhandled redirect storms during failovers.
const valkeyClient = new Redis('valkey://10.0.0.1:6379');

export async function transferBalance(senderId: string, receiverId: string, amount: number) {
  const script = `
    local senderBal = redis.call('GET', KEYS[1])
    if not senderBal or tonumber(senderBal) < tonumber(ARGV[1]) then
      return -1
    end
    redis.call('DECRBY', KEYS[1], ARGV[1])
    redis.call('INCRBY', KEYS[2], ARGV[1])
    return 0
  `;
  
  // BUG: senderId and receiverId map to random hash slots across the cluster
  // This triggers CROSSSLOT error and blocks failover transparent routing
  return await valkeyClient.eval(script, 2, `user:${senderId}:bal`, `user:${receiverId}:bal`, amount);
}
```

#### Production Standard (Correct)
> **Standard**: Employs hash-tagging `{tenant:${tenantId}}` to guarantee that both key candidates map to the exact same hash slot (0-16383). Uses a cluster-aware driver that automatically handles `MOVED` and `ASK` redirects with internal slot map caching, and enables pipelining to leverage Valkey 8.0's multi-threaded I/O engine without blocking coordinator execution.
```typescript
import { Cluster, RedisOptions } from 'ioredis';

const clusterNodes = [
  { host: '10.0.0.1', port: 6379 },
  { host: '10.0.0.2', port: 6379 },
  { host: '10.0.0.3', port: 6379 }
];

export const valkeyCluster = new Cluster(clusterNodes, {
  enableReadyCheck: true,
  maxRedirections: 16,
  scaleReads: 'master',
  slotsRefreshTimeout: 2000,
  redisOptions: {
    connectTimeout: 5000,
    keepAlive: 30000,
    enableAutoPipelining: true // Maximizes Valkey 8.0 threaded I/O throughput
  }
});

// SCRIPT INVARIANT: Keys co-located using shard routing key via hash tag
const TRANSFER_LUA = `
  local senderBal = redis.call('GET', KEYS[1])
  if not senderBal or tonumber(senderBal) < tonumber(ARGV[1]) then
    return -1
  end
  redis.call('DECRBY', KEYS[1], ARGV[1])
  redis.call('INCRBY', KEYS[2], ARGV[1])
  return 0
`;

export async function transferBalance(tenantId: string, senderId: string, receiverId: string, amount: number): Promise<number> {
  // Invariant: Both keys explicitly bound to the identical hash slot via {tenantId}
  const senderKey = `{tenant:${tenantId}}:user:${senderId}:bal`;
  const receiverKey = `{tenant:${tenantId}}:user:${receiverId}:bal`;

  const result = await valkeyCluster.eval(
    TRANSFER_LUA,
    2,
    senderKey,
    receiverKey,
    amount.toString()
  );

  return Number(result);
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Valkey Cluster Inspector MCP
Inspects Valkey 8.0 cluster topology, verifies slot distributions, monitors MOVED/ASK redirect rates, and evaluates threaded I/O buffer saturation.
Recommended Agent Skills (askills.dev)

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

valkey-cli Cluster Health Check
Runs automated cluster check commands (`valkey-cli --cluster check`) and slot allocation audits to prevent node desynchronization during failovers.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Valkey 8.0 Threaded I/O, Cluster Slot Redirects, and Multi-Key Scripting

Valkey 8.0 Threaded I/O, Cluster Slot Redirects, and Multi-Key Scripting defines an industrial-grade behavioral standard for backend engineering. Enforces strict production invariants for Valkey 8.0 deployments utilizing multi-threaded I/O, automated cluster failover, and atomic scripting. Mandates hash-tagging for multi-key atomicity, zero-drift MOVED and ASK redirect topology refreshes, and I/O pool configuration tuned to eliminate main-thread starvation. 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-tagged multi-key Lua scripts and executing blind retries on MOVED/ASK redirects during failover. 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-tagged multi-key Lua scripts and executing blind retries on MOVED/ASK redirects during failover.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 enforce hash tags (e.g., `{tenant

Engineers MUST ALWAYS enforce hash tags (e.g., `{tenant:42}:profile`, `{tenant:42}:settings`) on all keys involved in multi-key transactions (MGET, MSET) and Lua scripts to ensure co-location within the exact same hash slot (0-16383).

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 execute cross-slot Lua scripts or invoke `EVAL` with keys that resolve to different cluster slots, which will trigger runtime `CROSSSLOT Keys in request don't hash to the same slot` failures.

Engineers MUST NOT execute cross-slot Lua scripts or invoke `EVAL` with keys that resolve to different cluster slots, which will trigger runtime `CROSSSLOT Keys in request don't hash to the same slot` failures.

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 MUST handle `MOVED` and `ASK` redirects distinctly

Code MUST handle `MOVED` and `ASK` redirects distinctly: `MOVED` must trigger an asynchronous cluster topology cache refresh and re-route, whereas `ASK` must issue a one-off `ASKING` command directly to the designated target node without updating the local cluster slot map.

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 configure connection pooling and command pipelining to match Valkey 8.0's `io-threads` architecture, avoiding ephemeral connection churn that negates parallel socket read/write benefits.

Services MUST configure connection pooling and command pipelining to match Valkey 8.0's `io-threads` architecture, avoiding ephemeral connection churn that negates parallel socket read/write benefits.

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 or unbounded loops within Lua scripts

Components NEVER execute non-deterministic or unbounded loops within Lua scripts; while Valkey 8.0 parallelizes network I/O, script execution remains strictly pinned to the coordinator thread, risking cluster-wide heartbeat loss and false-positive failovers under execution blocks.

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 Redirects, and Multi-Key Scripting critical for AI coding assistants?

Enforces strict production invariants for Valkey 8.0 deployments utilizing multi-threaded I/O, automated cluster failover, and atomic scripting. Mandates hash-tagging for multi-key atomicity, zero-drift MOVED and ASK redirect topology refreshes, and I/O pool configuration tuned to eliminate main-thread starvation. 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-tagged multi-key Lua scripts and executing blind retries on MOVED/ASK redirects during failover.) 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