From 7ce494b262c158560aa02c2d26edbfc6bc2fb17c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Johan=20Andr=C3=A9n?= Date: Wed, 10 Jan 2018 11:43:05 +0100 Subject: [PATCH] A bit more text about the clustered receptionist --- akka-docs/src/main/paradox/actor-discovery-typed.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/akka-docs/src/main/paradox/actor-discovery-typed.md b/akka-docs/src/main/paradox/actor-discovery-typed.md index 74dff65671..bfa2856b87 100644 --- a/akka-docs/src/main/paradox/actor-discovery-typed.md +++ b/akka-docs/src/main/paradox/actor-discovery-typed.md @@ -52,5 +52,8 @@ guardian actor spawns a pinger to ping it. ## Cluster Receptionist -The `Receptionist` also works in a cluster, the state for the receptionist is propagated via @ref:[distributed data](distributed-data.md). -The only difference is the serialisation concerns, see @ref:[clustering](cluster-typed.md#serialization). +The `Receptionist` also works in a cluster, an actor registered to the receptionist will appear in the receptionist of the other nodes of the cluster. + +The state for the receptionist is propagated via @ref:[distributed data](distributed-data.md) which means that each node will eventually reach the same set of actors per `ServiceKey`. + +One important difference from a local only receptions is the serialisation concerns, all messages sent to and back from an actor on another node must be serializable, see @ref:[clustering](cluster-typed.md#serialization).