pekko/docs/src/main/paradox/cluster-singleton.md

Classic Cluster Singleton

@@includeincludes.md { #actor-api } For the full documentation of this feature and for new projects see @ref:Cluster Singleton.

Module info

To use Cluster Singleton, you must add the following dependency in your project:

@@dependency[sbt,Maven,Gradle] { bomGroup=org.apache.pekko bomArtifact=pekko-bom_scala.binary.version bomVersionSymbols=PekkoVersion symbol1=PekkoVersion value1="$pekko.version$" group=org.apache.pekko artifact=pekko-cluster-tools_scala.binary.version version=PekkoVersion }

@@project-info{ projectId="cluster-tools" }

Introduction

For the full documentation of this feature and for new projects see @ref:Cluster Singleton - Introduction.

The cluster singleton pattern is implemented by org.apache.pekko.cluster.singleton.ClusterSingletonManager. It manages one singleton actor instance among all cluster nodes or a group of nodes tagged with a specific role. ClusterSingletonManager is an actor that is supposed to be started as early as possible on all nodes, or all nodes with specified role, in the cluster. The actual singleton actor is started by the ClusterSingletonManager on the oldest node by creating a child actor from supplied Props. ClusterSingletonManager makes sure that at most one singleton instance is running at any point in time.

You can access the singleton actor by using the provided org.apache.pekko.cluster.singleton.ClusterSingletonProxy, which will route all messages to the current instance of the singleton. The proxy will keep track of the oldest node in the cluster and resolve the singleton's ActorRef by explicitly sending the singleton's actorSelection the org.apache.pekko.actor.Identify message and waiting for it to reply. This is performed periodically if the singleton doesn't reply within a certain (configurable) time. Given the implementation, there might be periods of time during which the ActorRef is unavailable, e.g., when a node leaves the cluster. In these cases, the proxy will buffer the messages sent to the singleton and then deliver them when the singleton is finally available. If the buffer is full the ClusterSingletonProxy will drop old messages when new messages are sent via the proxy. The size of the buffer is configurable and it can be disabled by using a buffer size of 0.

See @ref:Cluster Singleton - Potential problems to be aware of.

An Example

Assume that we need one single entry point to an external system. An actor that receives messages from a JMS queue with the strict requirement that only one JMS consumer must exist to make sure that the messages are processed in order. That is perhaps not how one would like to design things, but a typical real-world scenario when integrating with external systems.

Before explaining how to create a cluster singleton actor, let's define message classes @java[and their corresponding factory methods] which will be used by the singleton.

Scala

@@snip ClusterSingletonManagerSpec.scala { #singleton-message-classes }

Java

@@snip ClusterSingletonManagerTest.java { #singleton-message-classes }

On each node in the cluster you need to start the ClusterSingletonManager and supply the Props of the singleton actor, in this case the JMS queue consumer.

Scala

@@snip ClusterSingletonManagerSpec.scala { #create-singleton-manager }

Java

@@snip ClusterSingletonManagerTest.java { #create-singleton-manager }

Here we limit the singleton to nodes tagged with the "worker" role, but all nodes, independent of role, can be used by not specifying withRole.

We use an application specific terminationMessage @java[(i.e. TestSingletonMessages.end() message)] to be able to close the resources before actually stopping the singleton actor. Note that PoisonPill is a perfectly fine terminationMessage if you only need to stop the actor.

Here is how the singleton actor handles the terminationMessage in this example.

Scala

@@snip ClusterSingletonManagerSpec.scala { #consumer-end }

Java

@@snip ClusterSingletonManagerTest.java { #consumer-end }

With the names given above, access to the singleton can be obtained from any cluster node using a properly configured proxy.

Scala

@@snip ClusterSingletonManagerSpec.scala { #create-singleton-proxy }

Java

@@snip ClusterSingletonManagerTest.java { #create-singleton-proxy }

Configuration

For the full documentation of this feature and for new projects see @ref:Cluster Singleton - configuration.

Supervision

There are two actors that could potentially be supervised. For the consumer singleton created above these would be:

• Cluster singleton manager e.g. /user/consumer which runs on every node in the cluster
• The user actor e.g. /user/consumer/singleton which the manager starts on the oldest node

The Cluster singleton manager actor should not have its supervision strategy changed as it should always be running. However, it is sometimes useful to add supervision for the user actor. To accomplish this, add a parent supervisor actor which will be used to create the 'real' singleton instance. Below is an example implementation (credit to this StackOverflow answer)

Scala

@@snip ClusterSingletonSupervision.scala { #singleton-supervisor-actor }

Java

@@snip SupervisorActor.java { #singleton-supervisor-actor }

And used here

Scala

@@snip ClusterSingletonSupervision.scala { #singleton-supervisor-actor-usage }

Java

@@snip ClusterSingletonSupervision.java { #singleton-supervisor-actor-usage-imports } @@snip ClusterSingletonSupervision.java { #singleton-supervisor-actor-usage }

Lease

For the full documentation of this feature and for new projects see @ref:Cluster Singleton - Lease.