Patrik,
Specifically, we are using kubernetes and container based akka cluster,
where kubernetes will automatically restart any container that crashed.
I haven't got idea how to add "Down" logic before kubernetes restarts the
crashed container.
--
>> Read the docs:
Hi Justin,
No, I am trying to find where and when should I add the "Down" logic.
So I am trying to understand what would happen before I add the "Down"
logic.
On Friday, 26 May 2017 20:38:37 UTC+8, Justin du coeur wrote:
>
> Clarifying question: are you doing downing somewhere in this?
>
> The
One "way" to down a node is to restart it and join the cluster again with
same hostname:port. It will have a new UID and that is enough evidence for
automatic down of the old incarnation.
I agree with Justin, though. You probably need something more than just
restarting for proper downing. E.g.
Clarifying question: are you doing downing somewhere in this?
The naive auto-down feature shouldn't be used because it is *too* naive,
and leads to split-brain when you get transient network failures. But you
do still have to down nodes *somehow* when they crash, so that the system
knows to
I am using *akka cluster sharding *to build a long running calculation
service, and I have set auto-down to false.
And we have mechanism that *when one jvm get crashed it will be restarted
immediately* by some external monitoring tools.
I would like to confirm below behaviors when some jvm get
