Re: [akka-user] Downing Provider - Missing Unreachable messages

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

Re: [akka-user] Dispatcher configuration ?

Patrik, Thanks. I believe the issue is that i am using artery with docker https://groups.google.com/forum/#!msg/akka-user/Hp-Y2cHJwp8/Rz7bdti3BQAJ Also, i think it clearly reinforced in my mind the need to design so we can fail. Getting these failures helped me internalize this a little more.

Re: [akka-user] cluster sharding and auto-down

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.

Re: [akka-user] ActorPublisher GraphStage alternative?

In case it helps: https://groups.google.com/d/topic/akka-user/AgVHHnl9ub4/discussion https://github.com/akka/akka/issues/22742 On Fri, May 26, 2017 at 1:34 PM, Curt Siffert wrote: > > Hi, I see in the docs for 2.5.2 that ActorPublisher/ActorSubscriber will > be deprecated.