Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

Thanks for the information. I have read most of these. Can I take it from your responses that you agree that this could be a split brain problem? I am just wondering if using all nodes as seed nodes is what is causing the issue. In production our seed nodes are fixed IPs. But when we run in the

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

You asked for links http://doc.akka.io/docs/akka/2.4/scala/cluster-usage.html#Joining_to_Seed_Nodes http://doc.akka.io/docs/akka/2.4/scala/cluster-usage.html#Downing https://conductr.lightbend.com/docs/1.1.x/Home lör 10 sep. 2016 kl. 19:27 skrev Viktor Klang : >

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

ConductR* is designed to properly seed, and update, Akka Cluster based applications, and the Akka Split Brain Resolver provides deterministic partition handling. ConductR runs well on EC2: https://conductr.lightbend.com/docs/1.0.x/Install#EC2-Installation * ConductR and SBR are Lightbend

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

Problem is I need to prove the product in production before i can suggest purchase of expensive platforms. :) On Saturday, September 10, 2016 at 11:58:36 AM UTC-5, Justin du coeur wrote: > > On Sat, Sep 10, 2016 at 12:46 PM, kraythe > wrote: > >> I am not following you on

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

On Sat, Sep 10, 2016 at 12:46 PM, kraythe wrote: > I am not following you on this one. Is there a blog post or article you > can reference me to ? > > Thanks to you both. > > On Saturday, September 10, 2016 at 11:34:26 AM UTC-5, √ wrote: >> >> There's also ConductR + SBR >> >

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

I am not following you on this one. Is there a blog post or article you can reference me to ? Thanks to you both. On Saturday, September 10, 2016 at 11:34:26 AM UTC-5, √ wrote: > > There's also ConductR + SBR > > -- > Cheers, > √ > > On Sep 10, 2016 5:09 PM, "Patrik Nordwall"

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

There's also ConductR + SBR -- Cheers, √ On Sep 10, 2016 5:09 PM, "Patrik Nordwall" wrote: > Are you aware of the importance of the first seed node, the one you have > listed as first element in sees-nodes list? See documentation. > > You can get decent behavior if

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

Are you aware of the importance of the first seed node, the one you have listed as first element in sees-nodes list? See documentation. You can get decent behavior if you wait with joining until the list of discovered nodes stabilize, i.e. not changing within X seconds. Then sort them to make

[akka-user] Trigger some logic at the moment of TCP connection established

Hi guys, I'm trying to figure out on how to trigger some logic at the moment TCP connection established, and preferably *before traffic goes* Initial code looks like this: Tcp(system).outgoingConnection(???, ???).join(flow).runWith(source, sink) As far as I can see I need to access

Re: [akka-user] Akka Multithreading on Akka-Cluster

Your contribution makes ID strategy automatic even better, you know automatic = explicit + incremental right? So I think it would also work for your project, but I do understand why you have chosen explicit as you want to fail if you introduce a new class and forget to register it. I use