CLIENT NO-TOUCH
Controls whether commands sent by the client affect the LRU/LFU of accessed keys.
Browse all commands · Upstream source documentation
| Reference field | Value |
|---|---|
| Canonical name | CLIENT NO-TOUCH |
| Catalog group | Connection commands |
| Upstream since | 7.2.0 — upstream Redis/module version, not an ffkv release |
| Pinned catalog | Redis 8.10.0 |
Syntax
Section titled “Syntax”CLIENT NO-TOUCH <ON | OFF>ffkv behavior and limits
Section titled “ffkv behavior and limits”Connection state, selected database, authentication and protocol negotiation belong to the same persistent connection. RESP2 is the default; HELLO 3 selects RESP3. Streamed/unknown-length RESP3 frames are not supported.
Source: README.md:96–120, 391–395; tests/bdd/features/connections.feature.
All requests share the 8 MiB framing/1,024-argument ingress limit; normal RESP replies have 64 MiB wire/logical budgets with bounded nesting/value counts. Management and Lua origins impose smaller budgets. These are not a process RSS cap. Catalog inclusion is not exhaustive option or wire-format parity. See limits and compatibility.
Upstream metadata
Section titled “Upstream metadata”The following fields come from the pinned Redis metadata, not measured ffkv performance or an assertion that ffkv enforces every upstream flag. Running COMMAND INFO/COMMAND DOCS describe the current engine.
Upstream Redis complexity: O(1)
Upstream arity: 3 (includes the command name; a negative number is a minimum).
Command flags: NOSCRIPT, LOADING, STALE.
ACL categories: CONNECTION.
Argument structure
Section titled “Argument structure”| Argument | Type | Constraints / metadata |
|---|---|---|
enabled | oneof | Required |
↳ on | pure-token | token: ON |
↳ off | pure-token | token: OFF |
Additional pinned upstream metadata
{ "group": "connection", "since": "7.2.0"}Metadata source · Local snapshot: src/command_metadata.json, key client|no-touch.
BDD coverage and source examples
Section titled “BDD coverage and source examples”These are source observations, not a test run performed by this documentation build. A tag identifies scenario intent; an extracted vector identifies a command invocation, which may intentionally produce an error. Scenarios may require setup, multiple connections, persistence, cluster nodes or native-module fixtures.
- Eviction and key-touch policies are connection-local and visible in client flags —
tests/bdd/features/connections.feature:227; command tag and invocation observed.
Extracted command vectors
Section titled “Extracted command vectors”The following JSON arrays are the test harness’s argument vectors, not shell commands. Numeric arguments are converted by the harness; objects of the form {"base64":"…"} represent decoded binary bytes, not a literal JSON command argument. Preserve scenario setup and connection ordering. See the CLI guide for shell quoting and binary stdin. No reply is invented or inferred.
Eviction and key-touch policies are connection-local and visible in client flags — tests/bdd/features/connections.feature:246 (client “protected” executes:)
[ "CLIENT", "NO-TOUCH", "ON"]Next source assertion: the reply equals:
"OK"