You should probably also look into why they are quarantined.
It can be two reasons:
1) The nodes are removed from the cluster, which will happen if failure
detection triggers, you use auto-downing and they don't become reachable
again within the configured akka.cluster.auto-down-unreachable-after
Hi Mark,
On Tue, Feb 3, 2015 at 5:13 PM, Mark Kegel wrote:
> We are using akka 2.3.4, but I don't think this is an issue with a
> specific version of akka. In fact the docs explicitly state that you have
> to restart the akka node after its been Quarantined.
>
> I'm looking for some way to detec
We are using akka 2.3.4, but I don't think this is an issue with a specific
version of akka. In fact the docs explicitly state that you have to restart
the akka node after its been Quarantined.
I'm looking for some way to detect that my node has been quarantined so
that I can force an exit, so
What version of Akka are you using? We fixed some issue related to
quarantining in 2.3.9.
/Patrik
On Mon, Jan 26, 2015 at 5:20 PM, Mark Kegel wrote:
> We are using akka in a clustered configuration at work. Its a very simple
> cluster with just three node types: an admin node, "live" nodes, and
We are using akka in a clustered configuration at work. Its a very simple
cluster with just three node types: an admin node, "live" nodes, and
"preview" nodes. The admin node will manage nodes of the other two types,
and ask for things like status and uptime. Every so often one of the
live/prev
