Ir al contenido
Español

Receptionist

Esta página aún no está disponible en tu idioma.

Defined in: src/discovery/Receptionist.ts:83

Cluster-wide service registry. Each node hosts one Receptionist actor. Register/Deregister are authoritative locally; peers learn about registrations through periodic gossip carrying a delta of local keys.

When a peer node leaves, every key entry it contributed is removed and subscribers are notified with an updated Listing.

Subscriptions are bounded and watched. Both matter: Unsubscribe is caller-cooperative, so a crashed or adversarial subscriber used to sit in the set forever, and notifySubscribers walks that set on every registration change — an unbounded set is a memory leak and an O(N) cost on the hot path (#137).

  • Actor<ReceptionistInbox>

new Receptionist(options?): Receptionist

Defined in: src/discovery/Receptionist.ts:120

ReceptionistOptions = {}

Receptionist

Actor.constructor

displayName(): string

Defined in: src/Actor.ts:192

Human-readable name for this actor in log lines and in the DevTools actor tree (#891). Defaults to the full path — which is already the log source, so an actor that doesn’t override this logs exactly as it did before.

override displayName(): string { return `User(${this.entityId})`; }

Purely cosmetic. The path stays the identity everywhere that routes, correlates or aggregates — metric labels, tracing attributes, dead letters, ActorRef.toString(), every wire identifier — so a display name is free to be ambiguous, unstable, or shared between actors.

Resolved on every record, not captured once. Two consequences: keep it cheap and side-effect free, and expect it to be called before preStart (hence the optional chain — the context is attached after construction). In exchange a name may be derived from state, and it updates when that state does. Throwing, or returning anything but a non-empty string, falls back to the path and warns once: a naming hook must not be able to take a log line down with it.

ActorOptions.withDisplayName(...) outranks this, for the same reason withSupervisorStrategy(...) outranks supervisorStrategy — the spawn site is the more specific statement. It has to: every Behaviors actor is a TypedActor that inherits this default, so a method that won would silently swallow the spawn-site value for exactly the actors that have no subclass to override. For a name that only becomes known at runtime, this.context.setDisplayName(...) outranks both.

string

Actor.displayName


onReceive(message): void

Defined in: src/discovery/Receptionist.ts:162

Terminated is matched first, ahead of the protocol arms, and that order is load-bearing rather than stylistic: Subscribe and Unsubscribe are structurally identical (key + replyTo), so once Terminated sits behind them in the union ts-pattern can no longer tell which of the three an instanceOf arm extracts, and it hands the handler the wrong type. Taking the system message out of the union up front leaves the remaining arms exactly the shape they had before death watch existed.

ReceptionistInbox

void

Actor.onReceive


postRestart(_reason): void | Promise<void>

Defined in: src/Actor.ts:152

Called on the fresh instance after a restart. Default: call preStart().

Error

void | Promise<void>

Actor.postRestart


postStop(): void

Defined in: src/discovery/Receptionist.ts:147

Called after the actor has been terminated. Children are already stopped.

void

Actor.postStop


preRestart(_reason, _message?): void | Promise<void>

Defined in: src/Actor.ts:119

Called before a restart, on the instance about to be thrown away. The default calls postStop() and nothing else.

Override to release what the instance holds outside itself — a file handle, an open socket, a broker connection — or to do something other than drop the message that failed.

Stopping this actor’s children is not done here: the framework tears them down after this hook returns and waits for them before building the replacement, because postRestart re-runs preStart and a named child needs its name back. To keep the children instead, see Actor.stopChildrenOnRestart.

Error

ReceptionistInbox

void | Promise<void>

Actor.preRestart


preStart(): void

Defined in: src/discovery/Receptionist.ts:130

Called after construction and before the first message is processed.

void

Actor.preStart


stopChildrenOnRestart(): boolean

Defined in: src/Actor.ts:149

Whether a restart tears this actor’s children down before rebuilding it. Default: true.

A restart replaces the Actor instance while the cell — and therefore the child map — survives. Keeping the children was the old behaviour and it made an ordinary pattern impossible: postRestart re-runs preStart, so an actor that spawns a named child there hit Child name … is not unique on its first restart and never recovered (#634).

Override to false when the children are expensive to rebuild, hold state the parent cannot restore, or are supervised independently — a connection pool, say. They then outlive the restart exactly as before, and it is on you to make preStart idempotent — by adopting the survivor from the cell, this.child = this.context.child('name').toNullable() ?? this.context.spawn(Child, 'name'), or with context.spawnAnonymous. An instance field cannot do it: preStart runs on a fresh instance after every restart, so this.child ??= … is always unset and re-spawns into the name the surviving child still holds, which fails the spawn and restarts the actor again.

This is a separate hook rather than a preRestart override because the teardown has to be awaited: the new instance cannot be built until the old children are actually gone, and preRestart has no way to tell the cell that it started something worth waiting for.

boolean

Actor.stopChildrenOnRestart


supervisorStrategy(): SupervisorStrategy

Defined in: src/Actor.ts:160

Supervisor strategy for this actor’s children. Defaults to restart, up to 10 times per minute, then stop.

SupervisorStrategy

Actor.supervisorStrategy