Hello Jeroen,
Indeed the options that you have listed are the other available, thus
recommended, options. Truth be told, keeping a large cluster running does
require some more tooling, ops skills or people to take care of it.
In practice you could hook into monitoring services like Nagios or
Hi,
The docs also advice against auto-downing. However I do not really get the
alternative. Manual downing would be unworkable, because it could render your
application unavailable for to long. So should I implement some strategy in my
akka solution, or in some external monitoring system?
How
Hello
Is this situation can occur even if we have a small cluster like 3 instance
and all instances in seed list?
On Wednesday, 9 April 2014 08:46:38 UTC+3, Jem Mawson wrote:
Thank you Konrad. I'm really impressed by the depth of investigation and
your explanation.
On 8 April 2014
Hello Jem,
We looked deeper into this and it seems that it’s both working as mendated
by the current design (I’ll explain in detail bellow), as well as there is
a way of forcing your desired behaviour (which totally makes sense in some
scenarios).
Analysis:
First let’s dissect your log and see
Excellent analysis and suggestions, Konrad. One thing that this question
highlights is the importance of using auto-down with care, especially when
it is important to only have one singleton instance. If auto-down would not
have been used 39 would not have started the singleton before there was an
Hi Jem,
What version of Akka are you running? There is a regression in Akka 2.3.1 that
can cause issues with seed node joining.
It's also kind of hard to answer your question without some more information,
like a log printout.
B/
On 3 April 2014 at 03:37:14, Jem Mawson (jem.maw...@gmail.com)
