Re: [akka-user] Akka Streaming Java API- Cluster

[Björn Antonsson]

Hi Neeraj,

On 24 September 2014 at 08:10:58, tomerneeraj (tomer....@gmail.com) wrote:

Hi,

We developed our application on Akka (2.3.4). We are running 5 nodes in Akka Cluster where we are using cluster aware routers to distribute the traffic. Application seems to be worked fine when traffic is low but in case we increase traffic then out of memory and GC spike pops up. We fine tuned application using cluster dispatcher and heart beat timeout which seems to be settled to some extent but that is not the final solution

It sounds like you are accepting work faster than you can complete it. You must stop accept incoming work in some way.

While going through presentation by Victor and Dr Roland Akka Streaming seems to be solution here. We also went through Akka Pulling pattern(http://letitcrash.com/post/29044669086/balancing-workload-across-nodes-with-akka-2) but seems that Akka Streams is the one which can solve our problems here. Our team mainly have java developers with very little background on writing code in scala. We need to know couple of things mentioned below:

1. Does Akka Streams support Cluster aware Routers? If we want to migrate existing apps then any guidelines for that? If this can not be migrated then we are still okay to write code from scratch but in Akka streams examples written in scala we do not see use to cluster aware routers?

Streams are not actors. The cluster aware routers are built for actors. Actor messaging and streams are complementary technologies that can be used together, but you would need to redesign your application to use streams.

2. We also need to have auto scale functionality which we believe can be achieved by spawning new node in cluster i.e. putting this code in sender and check for time out of response. Any suggestion welcome here   

You can definitely start up new nodes based on some metric, but that needs to be done outside the cluster itself.

3. When Java API for Akka streaming planned to be released?

There is a blogpost outlining the roadmap here http://typesafe.com/blog/akka-roadmap-update-2014 but in short we aim for a an experimental release by the end of October and proper release early 2015.

B/

Regards
Neeraj

--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

-- 

Björn Antonsson

Typesafe – Reactive Apps on the JVM

twitter: @bantonsson

[tomerneeraj]

Hi Björn,

Just to get more details about our approach from here:

We plan to use Akka Streams during communication with remote actors (created through cluster aware routers). As of now communication with akka remote actors is through netty protocol. Will netty communication work here or we need to set up communication through Akka IO (Spray IO) for communication towards remote actors for enable back pressure?

Any pointers of using Akka streams between local actors within one JVM and remote actors(across JVM) will be really useful

Your thoughts please!!

Regards
Neeraj

[tomerneeraj]

Hi,

Any update on below approach?

=============================================

Just to get more details about our approach from here:

We plan to use Akka Streams during communication with remote actors (created through cluster aware routers). As of now communication with akka remote actors is through netty protocol. Will netty communication work here or we need to set up communication through Akka IO (Spray IO) for communication towards remote actors for enable back pressure?

Any pointers of using Akka streams between local actors within one JVM and remote actors(across JVM) will be really useful

Your thoughts please!!

Regards
Neeraj

On Wednesday, September 24, 2014 1:08:15 PM UTC+5:30, Björn Antonsson wrote:

[Björn Antonsson]

Hi,

On 26 September 2014 at 06:09:36, tomerneeraj (tomer....@gmail.com) wrote:

Hi,

Any update on below approach?

=============================================

Just to get more details about our approach from here:

We plan to use Akka Streams during communication with remote actors (created through cluster aware routers). As of now communication with akka remote actors is through netty protocol. Will netty communication work here or we need to set up communication through Akka IO (Spray IO) for communication towards remote actors for enable back pressure?

Using streams between cluster nodes sounds like a good plan. The streams over TCP that will be supported out of the box with akka streams will use the akka IO module.

Any pointers of using Akka streams between local actors within one JVM and remote actors(across JVM) will be really useful

The streams code is still evolving, and the API is about to change quite a bit, but you could look at the tests in this branch https://github.com/akka/akka/tree/release-2.3-dev/akka-stream-tests/src/test

B/