From 65a0ec4683de03523846a6c548f092c62432b8fe Mon Sep 17 00:00:00 2001 From: franciscolopezsancho Date: Tue, 7 Jul 2020 13:31:42 +0200 Subject: [PATCH] Clarify that receptionist supports clustering (#29352) --- akka-docs/src/main/paradox/typed/actor-discovery.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/akka-docs/src/main/paradox/typed/actor-discovery.md b/akka-docs/src/main/paradox/typed/actor-discovery.md index 98934a2942..13016f1364 100644 --- a/akka-docs/src/main/paradox/typed/actor-discovery.md +++ b/akka-docs/src/main/paradox/typed/actor-discovery.md @@ -28,9 +28,9 @@ applicable. ## Receptionist When an actor needs to be discovered by another actor but you are unable to put a reference to it in an incoming message, -you can use the `Receptionist`. You register the specific actors that should be discoverable -from other nodes in the local `Receptionist` instance. The API of the receptionist is also based on actor messages. -This registry of actor references is then automatically distributed to all other nodes in the cluster. +you can use the `Receptionist`. It supports both local and cluster(see @ref:[cluster](#cluster-receptionist)). You register the specific actors that should be discoverable +from each node in the local `Receptionist` instance. The API of the receptionist is also based on actor messages. +This registry of actor references is then automatically distributed to all other nodes in the case of a cluster. You can lookup such actors with the key that was used when they were registered. The reply to such a `Find` request is a `Listing`, which contains a `Set` of actor references that are registered for the key. Note that several actors can be registered to the same key.