raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

Clarify that receptionist supports clustering (#29352)

Browse source
This commit is contained in:
franciscolopezsancho 2020-07-07 13:31:42 +02:00 • committed by GitHub
parent 2f2ee9e67c
commit 65a0ec4683
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
akka-docs/src/main/paradox/typed/actor-discovery.md
View file

@ -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.