RESTORE-ASKING

An internal command for migrating keys in a cluster.

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	RESTORE-ASKING
Catalog group	Server commands
Upstream since	3.0.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

RESTORE-ASKING key ttl serialized-value [REPLACE] [ABSTTL]
  [IDLETIME seconds] [FREQ frequency]

ffkv behavior and limits

Server introspection describes ffkv, not a Redis process. MEMORY reports owned-allocation estimates, not jemalloc accounting. Administrative changes can affect all clients or persistent data; consult the scenario and operations guide before using destructive forms.

Source: README.md:393–395, 601–642; tests/bdd/features/server.feature; tests/bdd/features/catalog.feature.

Data-changing administration: use an isolated dataset or a verified backup. Lost replies have an unknown outcome; never blindly replay a destructive operation.

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

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) to create the new key and additional O(NM) to reconstruct the serialized value, where N is the number of Redis objects composing the value and M their average size. For small string values the time complexity is thus O(1)+O(1M) where M is small, so simply O(1). However for sorted set values the complexity is O(NMlog(N)) because inserting values into sorted sets is O(log(N)).

Upstream arity: -4 (includes the command name; a negative number is a minimum).

Command flags: WRITE, DENYOOM, ASKING.

ACL categories: KEYSPACE, DANGEROUS.

Documentation flags: SYSCMD.

Argument structure

Argument	Type	Constraints / metadata
key	key	key_spec_index: 0
ttl	integer	Required
serialized-value	string	Required
replace	pure-token	optional; token: REPLACE; since: 3.0.0
absttl	pure-token	optional; token: ABSTTL; since: 5.0.0
seconds	integer	optional; token: IDLETIME; since: 5.0.0
frequency	integer	optional; token: FREQ; since: 5.0.0

Key specifications

Upstream key discovery descriptors (indexes are relative to the full command vector):

[
  {
    "flags": [
      "OW",
      "UPDATE"
    ],
    "begin_search": {
      "index": {
        "pos": 1
      }
    },
    "find_keys": {
      "range": {
        "lastkey": 0,
        "step": 1,
        "limit": 0
      }
    }
  }
]

Additional pinned upstream metadata

{
  "group": "server",
  "since": "3.0.0",
  "history": [
    [
      "3.0.0",
      "Added the `REPLACE` modifier."
    ],
    [
      "5.0.0",
      "Added the `ABSTTL` modifier."
    ],
    [
      "5.0.0",
      "Added the `IDLETIME` and `FREQ` options."
    ]
  ]
}

Metadata source · Local snapshot: src/command_metadata.json, key restore-asking.

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.

• Restore-asking uses the same verified value payload and collision rules — tests/bdd/features/catalog.feature:212; command tag and invocation observed.

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.

Restore-asking uses the same verified value payload and collision rules — tests/bdd/features/catalog.feature:223 (I execute:)

[
  "RESTORE-ASKING",
  "destination",
  "0",
  {
    "saved": "payload"
  }
]

Next source assertion: the reply equals:

"OK"