CLUSTER MYID

Returns the ID of a node.

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	CLUSTER MYID
Catalog group	Cluster commands
Upstream since	3.0.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

CLUSTER MYID

ffkv behavior and limits

Requires —cluster-enabled. Hash slots, MOVED/ASK, membership, migration and failover use ffkv’s authenticated peer bus, not the Redis cluster bus. Do not attempt to join a Redis cluster. Tested behavior is not production-HA certification.

Source: README.md:625–642; tests/bdd/features/cluster.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

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: 2 (includes the command name; a negative number is a minimum).

Command flags: LOADING, STALE.

Additional pinned upstream metadata

{
  "group": "cluster",
  "since": "3.0.0"
}

Metadata source · Local snapshot: src/command_metadata.json, key cluster|myid.

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.

• Node and shard identities survive fsynced configuration and a crash — tests/bdd/features/cluster.feature:39; command tag and invocation observed.
• Soft reset preserves identity while hard reset regenerates it durably — tests/bdd/features/cluster.feature:829; 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.

Node and shard identities survive fsynced configuration and a crash — tests/bdd/features/cluster.feature:41 (node “node1” executes:)

[
  "CLUSTER",
  "MYID"
]

Next source assertion: the reply is a 40 character hexadecimal identifier