From 42b7e950f6cefc711c04a97bb60d0a2198844008 Mon Sep 17 00:00:00 2001 From: Aaron Stannard Date: Tue, 27 Apr 2021 08:45:05 -0500 Subject: [PATCH] Removed inaccurate warning from Cluster Singleton docs Cluster singletons won't create duplicates in a cluster split scenario, and it's much safer to run them _with_ a split brain resolver on than without. This documentation was just out of date. --- docs/articles/clustering/cluster-singleton.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/articles/clustering/cluster-singleton.md b/docs/articles/clustering/cluster-singleton.md index 7b31fcdd8a6..37c3e60a267 100644 --- a/docs/articles/clustering/cluster-singleton.md +++ b/docs/articles/clustering/cluster-singleton.md @@ -34,9 +34,6 @@ This pattern may seem to be very tempting to use at first, but it has several dr 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 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 be 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. @@ -111,4 +108,4 @@ akka.cluster.singleton-proxy { # Maximum allowed buffer size is 10000. buffer-size = 1000 } -``` \ No newline at end of file +```