Re: [akka-user] Re: node cannot automatically rejoin Cluster after seed node restarted

Yes, you're right. It works well if I make them both seed nodes. Thank you. On Friday, 8 July 2016 19:37:49 UTC+8, Patrik Nordwall wrote: > > When you restart node A it will join itself and form a separate cluster, > since you have not configured node B in the list of seed nodes. > > You are

Re: [akka-user] Re: node cannot automatically rejoin Cluster after seed node restarted

I'll do it your way. Thank you On Friday, 8 July 2016 19:48:55 UTC+8, Guido Medina wrote: > > Your nodes will re-join if you keep at least 1 seed node up while > restarting other nodes, try having 2 seed nodes. > In production don't ever relay on only 1 seed node, have at least 2. > > HTH, > >

[akka-user] How to unit test actors that are children of a cluster aware router actor?

Hi, I've got an app with akka clusters and sharding, where 'single' or per-node instance routing actors with many "child" actors being responsible for most of the message processing. I've been tasked with adding unit tests for the messages received by the "child" actors. I have Scalatest and

[akka-user] Pre-fusing and materialization

Is there a tutorial on how to optimize materialization somewhere? I've designed some logic that, for a given request, will aggregate multiple sources and stream the results back. When streaming large amounts of data, this isn't an issue, but we now have a use case that will request small chunks

[akka-user] Re: ANNOUNCE: New Remoting Milestone 3

Congratulations ! Sounds great. You guys are doing an amazing work. Will definitely give it a try. And I'm excited. On Friday, July 8, 2016 at 8:54:40 PM UTC+5:30, Patrik Nordwall wrote: > > Dear hakkers, > > > We are pleased to announce the availability of the third development > milestone

Re: [akka-user] ANNOUNCE: New Remoting Milestone 3

Very impressive, congratulations! > 8 juli 2016 kl. 17:24 skrev Patrik Nordwall : > > Dear hakkers, > > We are pleased to announce the availability of the third development > milestone of the new Akka Remoting, codenamed Artery. It’s an early > development preview

[akka-user] ANNOUNCE: New Remoting Milestone 3

Dear hakkers, We are pleased to announce the availability of the third development milestone of the new Akka Remoting, codenamed Artery. It’s an early development preview and we encourage you to try it out and give us feedback, but it’s not intended for production usage yet. The version number

[akka-user] ANNOUNCE: Akka 2.4.8 released!

Dear hakkers, we—the Akka committers—are proud to announce a new patch release of Akka 2.4. This release contains a number of fixes and improvements spread out across many of the Akka modules and the documentation. As usual, this version is a drop-in replacement for any previous 2.4.x

[akka-user] HelloAkka.java with gradle

Hi, I am new to Akka and Scala. I was trying out the HelloAkka.java program in eclipse. The program is here https://github.com/typesafehub/activator-hello-akka-java8/blob/master/src/main/java/HelloAkka.java Around the line 60 and 66, where we call Duration.create(), I get compilation error

[akka-user] Re: Node rejoin seed node failure after seed node restart

Thanks On Friday, July 8, 2016 at 7:51:59 PM UTC+8, Guido Medina wrote: > > *Copy & paste from the other thread* > > Your nodes will re-join if you keep at least 1 seed node up while > restarting other nodes, try having 2 seed nodes. > In production don't ever relay on only 1 seed node, have

[akka-user] Re: Node rejoin seed node failure after seed node restart

*Copy & paste from the other thread* Your nodes will re-join if you keep at least 1 seed node up while restarting other nodes, try having 2 seed nodes. In production don't ever relay on only 1 seed node, have at least 2. HTH, Guido. On Friday, July 8, 2016 at 11:44:52 AM UTC+1, 谌浏洋 wrote:

[akka-user] Re: Node rejoin seed node failure after seed node restart

You posted this question in another thread, please go there and look. On Friday, July 8, 2016 at 11:44:52 AM UTC+1, 谌浏洋 wrote: > > Sorry for my poor English > > I started two node A(seed) B, Both A and B can communication to each other. > > When I restart node A. node B cannot join A anymore. (No

Re: [akka-user] Re: node cannot automatically rejoin Cluster after seed node restarted

Your nodes will re-join if you keep at least 1 seed node up while restarting other nodes, try having 2 seed nodes. In production don't ever relay on only 1 seed node, have at least 2. HTH, Guido. On Friday, July 8, 2016 at 12:37:49 PM UTC+1, Patrik Nordwall wrote: > > When you restart node A

Re: [akka-user] Re: node cannot automatically rejoin Cluster after seed node restarted

When you restart node A it will join itself and form a separate cluster, since you have not configured node B in the list of seed nodes. You are not using any downing strategy so node B will not remove node

Re: [akka-user] How would you "connect" many independent graphs maintaining backpressure between them?

Considered Flow.throttle? On Fri, Jul 8, 2016 at 11:23 AM, Jack Daniels wrote: > up vote > down votefavorite > > > Hey guys! I continue learning

[akka-user] How would you "connect" many independent graphs maintaining backpressure between them?

up vote down votefavorite Hey guys! I continue learning akka-streams and have new question . *Variables:* - Single http

[akka-user] node cannot automatically rejoin Cluster after seed node restarted

Hi, there The case is based on akka-sample-cluster-scala I changed it to only 2 nodes and started them separately: A - seed node @ 2551 B - node @