I think it would be better to expose more details from the Reachability
state and then that information can be interpreted in various smart ways
depending on what is needed.
/Patrik
On Sat, May 27, 2017 at 10:12 PM, Michal Borowiecki <
michal.borowie...@openbet.com> wrote:
> Hi Patrik,
>
> I thi
Hi Patrik,
I think indeed that is what we're seeing. It happened in production and
we can easily reproduce it by bringing down network connections one at a
time.
However, I wonder if this is something that could be solved in akka
itself, as opposed to trying to implement a custom downing pro
Such asymmetric splits can be problematic, because the unreachability
information is spread via the gossip. E.g A2 detecting B1 to be unreachable
and that is spread to A3-B3-C3 which will start ignoring gossip messages
from B1 even though they have some connectivity. I'm not sure if that is
what yo
Hi everyone,
Straight to the point, the scenario is the following, I've got the
following cluster :
Host 1) Nodes A1 - B1 - C1
Host 2) Nodes A2 - B2 - C2
Host 3) Nodes A3 - B3 - C3
Where :
Nodes AX and BX are singletons
Nodes CX are worker routers
I'm writing a downing provider to handle the
