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

Merge pull request #2126 from ktoso/3986-cluster-singleton-may-become-doubleton-during-splits-ktoso

Browse source 
=doc #3986 Cluster Singleton should not be used with AutoDown
This commit is contained in:
Konrad Malawski 2014-04-10 15:39:31 +02:00
commit 2173a037cb
3 changed files with 24 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
akka-contrib/docs/cluster-singleton.rst
View file

@ -48,6 +48,26 @@ is able to identify the singleton. It's worth noting that messages can always be
distributed nature of these actors. As always, additional logic should be implemented in the singleton
(acknowledgement) and in the client (retry) actors to ensure at-least-once message delivery.
Potential problems to be aware of
---------------------------------
This pattern may seem to be very tempting to use at first, but it has several drawbacks, some of them are listed below:
* the cluster singleton may quickly become a *performance bottleneck*,
* you can not rely on the cluster singleton to be *non-stop* available - e.g. when node on which the singleton was running dies,
it will take a few seconds for this to be noticed and the singleton be migrated to another node,
* in the case of a network partition appearing in a Cluster that is using Automatic Downing (:ref:`automatic-vs-manual-downing-scala`),
it may happen that the isolated clusters each decide to spin up their own singleton, meaning that there might be multiple
singletons running in the system, yet the Clusters have no way of finding out about them (because of the network partition).
Especially the last point is something you should be aware of - in general when using the Cluster Singleton pattern
you should take care of downing nodes yourself and not rely on the timing based auto-down feature.
.. warning::
**Be very careful when using Cluster Singleton together with Automatic Downing**,
since it allows the cluster to split up into two separate clusters, which in turn will result
in *multiple Singletons* being started - one in each separate cluster!
An Example
----------

2
akka-docs/rst/java/cluster-usage.rst
View file

@ -111,6 +111,8 @@ cluster or to join the same cluster again. It can use the same host name and por
after the restart, but it must have been removed from the cluster before the join
request is accepted.
.. _automatic-vs-manual-downing-java:
Automatic vs. Manual Downing
^^^^^^^^^^^^^^^^^^^^^^^^^^^^

2
akka-docs/rst/scala/cluster-usage.rst
View file

@ -105,6 +105,8 @@ cluster or to join the same cluster again. It can use the same host name and por
after the restart, but it must have been removed from the cluster before the join
request is accepted.
.. _automatic-vs-manual-downing-scala:
Automatic vs. Manual Downing
^^^^^^^^^^^^^^^^^^^^^^^^^^^^