date:20170525

[akka-user] Akka stream - Source of http response.

2017-05-25 Thread Alejandro Merchan

Hi everybody.

One question, how is possible create a continuous Source from http client 
response?

thanks !!

-- 
>>  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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] ANNOUNCE: New documentation theme and Akka HTTP 10.0.7 Released

2017-05-25 Thread Konrad Malawski

Dear hakkers,

We are proud to announce Akka Http 10.0.7, which is the seventh release of
the Akka Http 10.0 series. This is a regular maintenance release that
contains several maintenance fixes, improvements and features that are a
result of our ongoing collaboration with the Play team towards making Akka
HTTP the default backend in Play’s upcoming major release.
Notable changes

A total 29 issues were closed since 10.0.6. Out of those, the most notable
ones are listed below.

You can view the complete list of closed issues can be found on the 10.0.7
 milestone on
github.

*New documentation theme (aligned with new theme in Akka)*

Today, as follow up to yesterday’s Akka 2.5.2 release
, Akka HTTP also
moves to using the new documentation theme. This is the first step towards
even more simplification and restructuring of the documentation such that
everything is simple to find, and also being able to add more practical
examples in the future.

We are aware that the search functionality is currently non-operational,
and are working towards resolving it. The indexing mechanism of the 3rd
party search engine is not yet able to work with our new structure - please
be patient for a little while while we resolve this issue.

*New Seed Templates for Akka HTTP Apps*

We prepared new seed templates for starting out with Akka HTTP using the Java
DSL  as well as Scala DSL
. By using the sbt new
command one can now easily get a small sample project to easily get started
with your first Akka HTTP app. More instructions on the seed template pages.

*New Path Directive **ignoreTrailingSlash***

Akka HTTP treats differently by default a route that ends with slash (/)
than one that doesn’t. From this version on, users who don’t want to have
this distinction, can use a new Path Directive called ignoreTrailingSlash.
This route, will retry its inner route with and without a trailing slash.
If you want to know more about this feature, please check the documentation
pages for Scala and Java API.
List of Changes

Improvements

akka-http

   - Added new Path Directive ignoreTrailingSlash (#880
   )
   - Prepared new seed templates for Akka HTTP apps (for both Java DSL
    and Scala DSL
   ) (#1137
   & #1055
   )
   - Migrated to the new docs theme (same as Akka) (#1129
   )
   - (ApiMayChange) HttpApp#route method was renamed to routes to highlight
   it is “all the routes” (#953
   )

akka-http2-support

   - Synthetic Remote-Address header setting is now honored in HTTP2 server
   blueprint (#1088 )

Bug Fixes

General

   - OSGi Import-Package ranges have been fixed to allow Akka 2.5.x #1097
   

akka-http-core

   - Dates in RFC1123 format with single-digit-day are now properly parsed
   #1110 

Compatibility notes

This version is compatible with Akka 2.4.x as well as the current 2.5.1, so
we encourage you to use Akka 2.5 with this version, as the new completely
redesigned materializer in Akka Streams can result in various performance
and memory usage improvements across the board.

If you want to use Akka HTTP together with Akka 2.5.1 make sure to include
a dependency to akka-stream 2.5.1 and not only to akka-actor 2.5.1
(otherwise, your app may fail at runtime because of incompatibilities
between a 2.4.x version of akka-stream and a 2.5.x version of akka-actor).

Akka 10.0.x is backwards binary compatible with previous 10.0.x releases
and Akka 2.4.x. This means that the new JARs are a drop-in replacement for
the old one (but not the other way around) as long as your build does not
enable the inliner (Scala-only restriction). It should be noted that Scala
2.12.x is is not binary compatible with Scala 2.11.x.
Credits

For this release we had the help of 12 contributors – thank you all very
much!

commits  added  removed
 17212  581 Jonas Fonseca
 12 70  104 Johannes Rudolph
  7230   44 Konrad `ktoso` Malawski
  3381   42 Josep Prat
  1 626 Erwan Loisant
  1  0   28 Richard Imaoka
  1 251 surendranath chowdary
  1 250 bobba surendranath chowdary
  1  9   11 Björn Antonsson
  1  76 michael-smith
  1  22 André Rüdiger
  1  21 Arnout Engelen


Happy hakking!

– The Akka Team

-- 
>>

Re: [akka-user] Akka Distributed Data Sample thowing OversizedPayloadException

2017-05-25 Thread Patrik Nordwall

Yes, it will be fixed. I don't think it will cause any critical problems.
It's only when you do updates at a high rate and then the delta messages
will be dropped. Delivery of deltas are not mandatory for correct end
result. Make sure you use latest version, though. 2.5.2.

If it's annoying you can disable deltas until it's fixed.

That said, I think it's an important issue to fix soon. Thanks for
reporting.

/Patrik
tors 25 maj 2017 kl. 17:35 skrev Mainak Ghosh :

> Hello Patrik,
>
> Will this bug be fixed? Can you suggest me some quick work around?
>
> Thanks,
> Mainak
>
> On Wed, May 24, 2017 at 8:24 AM, Patrik Nordwall <
> patrik.nordw...@gmail.com> wrote:
>
>> That's interesting. I see the same problem when running that example. It
>> shouldn't be much data involved there. I have created issue
>> https://github.com/akka/akka-samples/issues/25 and will look into it.
>>
>> /Patrik
>>
>> On Tue, May 23, 2017 at 7:25 PM, Mainak Ghosh 
>> wrote:
>>
>>> Hey Patrick,
>>>
>>> I might have pasted the wrong log. Here is the correct one:
>>>
>>> [JVM-1] [INFO] [05/22/2017 16:31:25.245] [ScalaTest-main]
>>> [akka.remote.Remoting] Starting remoting
>>> [JVM-3] [INFO] [05/22/2017 16:31:25.245] [ScalaTest-main]
>>> [akka.remote.Remoting] Starting remoting
>>> [JVM-2] [INFO] [05/22/2017 16:31:25.355] [ScalaTest-main]
>>> [akka.remote.Remoting] Starting remoting
>>> [JVM-3] [INFO] [05/22/2017 16:31:25.665] [ScalaTest-main]
>>> [akka.remote.Remoting] Remoting started; listening on addresses
>>> :[akka.tcp://VotingServiceSpec@localhost:56966]
>>> [JVM-3] [INFO] [05/22/2017 16:31:25.681] [ScalaTest-main]
>>> [akka.remote.Remoting] Remoting now listens on addresses:
>>> [akka.tcp://VotingServiceSpec@localhost:56966]
>>> [JVM-3] [INFO] [05/22/2017 16:31:25.696] [ScalaTest-main]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56966] - Starting up...
>>> [JVM-1] [INFO] [05/22/2017 16:31:25.728] [ScalaTest-main]
>>> [akka.remote.Remoting] Remoting started; listening on addresses
>>> :[akka.tcp://VotingServiceSpec@localhost:56969]
>>> [JVM-1] [INFO] [05/22/2017 16:31:25.728] [ScalaTest-main]
>>> [akka.remote.Remoting] Remoting now listens on addresses:
>>> [akka.tcp://VotingServiceSpec@localhost:56969]
>>> [JVM-1] [INFO] [05/22/2017 16:31:25.747] [ScalaTest-main]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56969] - Starting up...
>>> [JVM-3] [INFO] [05/22/2017 16:31:25.830] [ScalaTest-main]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56966] - Registered cluster JMX
>>> MBean [akka:type=Cluster]
>>> [JVM-3] [INFO] [05/22/2017 16:31:25.830] [ScalaTest-main]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56966] - Started up successfully
>>> [JVM-2] [INFO] [05/22/2017 16:31:25.861] [ScalaTest-main]
>>> [akka.remote.Remoting] Remoting started; listening on addresses
>>> :[akka.tcp://VotingServiceSpec@localhost:56978]
>>> [JVM-2] [INFO] [05/22/2017 16:31:25.861] [ScalaTest-main]
>>> [akka.remote.Remoting] Remoting now listens on addresses:
>>> [akka.tcp://VotingServiceSpec@localhost:56978]
>>> [JVM-3] [INFO] [05/22/2017 16:31:25.861]
>>> [VotingServiceSpec-akka.actor.default-dispatcher-5]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56966] - No seed-nodes
>>> configured, manual cluster join required
>>> [JVM-2] [INFO] [05/22/2017 16:31:25.892] [ScalaTest-main]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56978] - Starting up...
>>> [JVM-1] [INFO] [05/22/2017 16:31:25.906] [ScalaTest-main]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56969] - Registered cluster JMX
>>> MBean [akka:type=Cluster]
>>> [JVM-1] [INFO] [05/22/2017 16:31:25.906] [ScalaTest-main]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56969] - Started up successfully
>>> [JVM-1] [INFO] [05/22/2017 16:31:25.921]
>>> [VotingServiceSpec-akka.actor.default-dispatcher-8]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56969] - No seed-nodes
>>> configured, manual cluster join required
>>> [JVM-2] [INFO] [05/22/2017 16:31:26.073] [ScalaTest-main]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56978] - Registered cluster JMX
>>> MBean [akka:type=Cluster]
>>> [JVM-2] [INFO] [05/22/2017 16:31:26.073] [ScalaTest-main]
>>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>>> [akka.tcp://VotingServiceSpec@localhost:56978] - Started up successfully
>>> [JVM-2] [INFO] [05/22/2017

[akka-user] Dispatcher configuration ?

2017-05-25 Thread Vishnu Vardhan

Hi,

I posted earlier here 
https://groups.google.com/forum/#!topic/akka-user/7jwQC7vuYQs but i wanted 
to reframe what i think is going on and seek some advice.

The code is available on GitHub if anybody is 
interested. https://github.com/vardhanv/cosbench_ng

Essentially, i am writing an S3 performance tester. Because it is a 
performance tester it needs to scale.. 

My architecture is
- An akka cluster, with a singleton consistent hashing router
- Many slaves running on other servers (default is 2 slave workers per host)
- An akka streams implementation that is routing jobs to the slaves 
(gets/PUTs) etc
- Slave workers that receive the commands and forward them to 
   - a stateless S3 scala object that does blocking S3 PUTs - but is 
protected by a custom thread pool executor with 40 threads

My default test setup is "one server that also has two slaves, and one 
agent that hosts two more slaves - for a total of 4 slaves".

All this in docker containers, so that deployment is simple.

I believe that the inconsistent behavior i am seeing with startup, message 
passing, unexpected shutdowns are to do with how these various pieces and 
their threads are getting scheduled.

I am wondering if my hypothesis is true, and what can i do to protect these 
components from each other (cluster message passing, from stream messages, 
from the blocking calls)

Best Regards
Vishnu



-- 
>>  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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka Distributed Data Sample thowing OversizedPayloadException

2017-05-25 Thread Mainak Ghosh

Hello Patrik,

Will this bug be fixed? Can you suggest me some quick work around?

Thanks,
Mainak

On Wed, May 24, 2017 at 8:24 AM, Patrik Nordwall 
wrote:

> That's interesting. I see the same problem when running that example. It
> shouldn't be much data involved there. I have created issue
> https://github.com/akka/akka-samples/issues/25 and will look into it.
>
> /Patrik
>
> On Tue, May 23, 2017 at 7:25 PM, Mainak Ghosh 
> wrote:
>
>> Hey Patrick,
>>
>> I might have pasted the wrong log. Here is the correct one:
>>
>> [JVM-1] [INFO] [05/22/2017 16:31:25.245] [ScalaTest-main]
>> [akka.remote.Remoting] Starting remoting
>> [JVM-3] [INFO] [05/22/2017 16:31:25.245] [ScalaTest-main]
>> [akka.remote.Remoting] Starting remoting
>> [JVM-2] [INFO] [05/22/2017 16:31:25.355] [ScalaTest-main]
>> [akka.remote.Remoting] Starting remoting
>> [JVM-3] [INFO] [05/22/2017 16:31:25.665] [ScalaTest-main]
>> [akka.remote.Remoting] Remoting started; listening on addresses
>> :[akka.tcp://VotingServiceSpec@localhost:56966]
>> [JVM-3] [INFO] [05/22/2017 16:31:25.681] [ScalaTest-main]
>> [akka.remote.Remoting] Remoting now listens on addresses:
>> [akka.tcp://VotingServiceSpec@localhost:56966]
>> [JVM-3] [INFO] [05/22/2017 16:31:25.696] [ScalaTest-main]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56966] - Starting up...
>> [JVM-1] [INFO] [05/22/2017 16:31:25.728] [ScalaTest-main]
>> [akka.remote.Remoting] Remoting started; listening on addresses
>> :[akka.tcp://VotingServiceSpec@localhost:56969]
>> [JVM-1] [INFO] [05/22/2017 16:31:25.728] [ScalaTest-main]
>> [akka.remote.Remoting] Remoting now listens on addresses:
>> [akka.tcp://VotingServiceSpec@localhost:56969]
>> [JVM-1] [INFO] [05/22/2017 16:31:25.747] [ScalaTest-main]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56969] - Starting up...
>> [JVM-3] [INFO] [05/22/2017 16:31:25.830] [ScalaTest-main]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56966] - Registered cluster JMX
>> MBean [akka:type=Cluster]
>> [JVM-3] [INFO] [05/22/2017 16:31:25.830] [ScalaTest-main]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56966] - Started up successfully
>> [JVM-2] [INFO] [05/22/2017 16:31:25.861] [ScalaTest-main]
>> [akka.remote.Remoting] Remoting started; listening on addresses
>> :[akka.tcp://VotingServiceSpec@localhost:56978]
>> [JVM-2] [INFO] [05/22/2017 16:31:25.861] [ScalaTest-main]
>> [akka.remote.Remoting] Remoting now listens on addresses:
>> [akka.tcp://VotingServiceSpec@localhost:56978]
>> [JVM-3] [INFO] [05/22/2017 16:31:25.861] 
>> [VotingServiceSpec-akka.actor.default-dispatcher-5]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56966] - No seed-nodes
>> configured, manual cluster join required
>> [JVM-2] [INFO] [05/22/2017 16:31:25.892] [ScalaTest-main]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56978] - Starting up...
>> [JVM-1] [INFO] [05/22/2017 16:31:25.906] [ScalaTest-main]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56969] - Registered cluster JMX
>> MBean [akka:type=Cluster]
>> [JVM-1] [INFO] [05/22/2017 16:31:25.906] [ScalaTest-main]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56969] - Started up successfully
>> [JVM-1] [INFO] [05/22/2017 16:31:25.921] 
>> [VotingServiceSpec-akka.actor.default-dispatcher-8]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56969] - No seed-nodes
>> configured, manual cluster join required
>> [JVM-2] [INFO] [05/22/2017 16:31:26.073] [ScalaTest-main]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56978] - Registered cluster JMX
>> MBean [akka:type=Cluster]
>> [JVM-2] [INFO] [05/22/2017 16:31:26.073] [ScalaTest-main]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56978] - Started up successfully
>> [JVM-2] [INFO] [05/22/2017 16:31:26.104] 
>> [VotingServiceSpec-akka.actor.default-dispatcher-3]
>> [akka.cluster.Cluster(akka://VotingServiceSpec)] Cluster Node
>> [akka.tcp://VotingServiceSpec@localhost:56978] - No seed-nodes
>> configured, manual cluster join required
>> [JVM-1] [INFO] [05/22/2017 16:31:26.260] [ScalaTest-main]
>> [VotingServiceSpecMultiJvmNode1(akka://VotingServiceSpec)] Role [node-1]
>> started with address [akka.tcp://VotingServiceSpec@localhost:56969]
>> [JVM-2] [INFO] [05/22/2017 16:31:26.338] [ScalaTest-main]
>> [VotingServiceSpecMultiJvmNode2(akka://VotingServiceSpec)] Role [node-2]
>>

[akka-user] cluster heartbeat delay

2017-05-25 Thread Yutao Shuai

We have a 3-node cluster （157,158 and 159）, we send 4000messages/s to 158 
in 157, sometimes 157 can not receive the heartbeat from 158, but 158 is 
already sent the heartbeat. The heartbeat between 159 and 158 is fine, and 
157-159 also ok. Our version is akka2.3.10, and hope to be able to solve 
this problem in this version, although we will soon be upgraded to 2.4.18

Here is the log of heartbeat, we add a log when receive heartbeat.
This is 157 log, as we can see, 157 can not receive the heartbeat from 158 
since 20:59:15,985 until 20:59:32,558, Heartbeat is not lost but delay


2017-05-23 20:59:07,516 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:08,601 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:11,824 | DEBUG | t-dispatcher-852 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:13,004 | DEBUG | lt-dispatcher-29 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:13,166 | DEBUG | t-dispatcher-853 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:13,273 | DEBUG | t-dispatcher-853 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:14,287 | DEBUG | t-dispatcher-853 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:15,853 | DEBUG | t-dispatcher-853 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:15,985 | DEBUG | t-dispatcher-852 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,558 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,612 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,632 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,831 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,910 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,982 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,987 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,059 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,101 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,170 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,175 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,190 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,224 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from

[akka-user] AKKA cluster heartbeat delay

2017-05-25 Thread Yutao Shuai

We have a 3 nodes cluster （157,158 and 159）, we send 4000 messages per 
seconds to 158 in 157, sometimes 157 can not receive the heartbeat from 
158, but 158 is already sended. The heartbeat between 159 and 158 is fine, 
and 157-159 also ok. Our version is akka2.3.10, and we want to solve this 
problem in 2.3.10, we will upgrade to 2.4.18 soon.

Here is the log of heartbeat, we add a log when receive heartbeat.
This is 157 log, as we can see, 157 can not receive the heartbeat from 158 
since 20:59:15,985 until 20:59:32,558, Heartbeat is not lost but delay


2017-05-23 20:59:07,516 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:08,601 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:11,824 | DEBUG | t-dispatcher-852 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:13,004 | DEBUG | lt-dispatcher-29 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:13,166 | DEBUG | t-dispatcher-853 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:13,273 | DEBUG | t-dispatcher-853 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:14,287 | DEBUG | t-dispatcher-853 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:15,853 | DEBUG | t-dispatcher-853 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:15,985 | DEBUG | t-dispatcher-852 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,558 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,612 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,632 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,831 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,910 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,982 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:32,987 | DEBUG | ult-dispatcher-3 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,059 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,101 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,170 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,175 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,190 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from 
akka.tcp://actorsystem@192.168.0.158:2551
2017-05-23 20:59:33,224 | DEBUG | ult-dispatcher-2 | 
ClusterHeartbeatReceiver |apply$mcV$sp() 77 | 
com.typesafe.akka.slf4j | Received Heartbeat from

Re: [akka-user] Re: Issue in Sending messages through akka cluster.

2017-05-25 Thread chaitanya

We used Single Producer and Multiple Consumer pattern

On Thursday, 25 May 2017 15:56:15 UTC+5:30, chaitanya wrote:
>
> " The buffers in Artery are bounded and will start dropping messages if 
> overwhelmed " -
>
> which pattern would be best to resolve this issue and faster?
>
>
> On Wednesday, 24 May 2017 17:54:11 UTC+5:30, Patrik Nordwall wrote:
>>
>> You have to implement some flow control, such as as using the "Work 
>> Pulling" pattern 
>> ,
>>  
>> throttling, or send acknowledgment messages back from the consumer. If 
>> producer is sending messages at a higher rate than they can be consumed 
>> those messages must be buffered somewhere and that can eventually result in 
>> out of memory. The buffers in Artery are bounded and will start dropping 
>> messages if overwhelmed.
>>
>> Cheers, 
>> Patrik
>>
>> On Wed, May 24, 2017 at 9:57 AM, chaitanya  wrote:
>>
>>> Following is the console output of my program it says Dropping messages 
>>> due to overflow of send queue. How to solve this? 
>>>
>>>  GET Messages   >>> Content
>>>  GET Messages   >>> Content
>>> 12:49:35.091 [ClusterSystem-akka.actor.default-dispatcher-3] DEBUG 
>>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>>> [ActorSelectionMessage(java.lang.String)] from 
>>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>>> [3072]
>>> 12:49:35.092 [ClusterSystem-akka.actor.default-dispatcher-3] DEBUG 
>>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>>> [ActorSelectionMessage(java.lang.String)] from 
>>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>>> [3072]
>>> 12:49:35.092 [ClusterSystem-akka.actor.default-dispatcher-3] DEBUG 
>>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>>> [ActorSelectionMessage(java.lang.String)] from 
>>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>>> [3072]
>>> 12:49:35.092 [ClusterSystem-akka.actor.default-dispatcher-3] INFO 
>>>  a.r.RemoteActorRefProvider$RemoteDeadLetterActorRef - Message 
>>> [java.lang.String] from 
>>> Actor[akka://ClusterSystem/user/master_1#-495216506] to 
>>> Actor[akka://ClusterSystem/deadLetters] was not delivered. [1] dead letters 
>>> encountered. This logging can be turned off or adjusted with configuration 
>>> settings 'akka.log-dead-letters' and 
>>> 'akka.log-dead-letters-during-shutdown'.
>>> 12:49:35.093 [ClusterSystem-akka.actor.default-dispatcher-3] INFO 
>>>  a.r.RemoteActorRefProvider$RemoteDeadLetterActorRef - Message 
>>> [java.lang.String] from 
>>> Actor[akka://ClusterSystem/user/master_1#-495216506] to 
>>> Actor[akka://ClusterSystem/deadLetters] was not delivered. [2] dead letters 
>>> encountered. This logging can be turned off or adjusted with configuration 
>>> settings 'akka.log-dead-letters' and 
>>> 'akka.log-dead-letters-during-shutdown'.
>>> 12:49:35.093 [ClusterSystem-akka.actor.default-dispatcher-2] DEBUG 
>>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>>> [ActorSelectionMessage(java.lang.String)] from 
>>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>>> [3072]
>>> 12:49:35.095 [ClusterSystem-akka.actor.default-dispatcher-2] DEBUG 
>>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>>> [ActorSelectionMessage(java.lang.String)] from 
>>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>>> [3072]
>>> 12:49:35.097 [ClusterSystem-akka.actor.default-dispatcher-2] DEBUG 
>>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>>> [ActorSelectionMessage(java.lang.String)] from 
>>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>>> [3072]
>>>
>>> How can 
>>>
>>> On Wednesday, 24 May 2017 00:05:42 UTC+5:30, chaitanya wrote:

 Hi guys,'
 I am a newbie to akka cluster  and  i have created a sample program. I 
 am using producer consumer pattern. My producer sends messages to consumer 
 which are 2 seed nodes.
 The program works fine when no of messages are less like in thousands 
 but the program seems to seize when i send huge no of messages to seed 
 nodes. 

 I have implemented artery remoting and for this i refer to  
 http://doc.akka.io/docs/akka/2.5/java/remoting-artery.html

 Please find project in attached zip. Can anyone please help me out with 
 this 

 -- 
>>> >> Read the

Re: [akka-user] Re: Issue in Sending messages through akka cluster.

2017-05-25 Thread chaitanya

" The buffers in Artery are bounded and will start dropping messages if 
overwhelmed " -

which pattern would be best to resolve this issue and faster?


On Wednesday, 24 May 2017 17:54:11 UTC+5:30, Patrik Nordwall wrote:
>
> You have to implement some flow control, such as as using the "Work 
> Pulling" pattern 
> ,
>  
> throttling, or send acknowledgment messages back from the consumer. If 
> producer is sending messages at a higher rate than they can be consumed 
> those messages must be buffered somewhere and that can eventually result in 
> out of memory. The buffers in Artery are bounded and will start dropping 
> messages if overwhelmed.
>
> Cheers, 
> Patrik
>
> On Wed, May 24, 2017 at 9:57 AM, chaitanya  > wrote:
>
>> Following is the console output of my program it says Dropping messages 
>> due to overflow of send queue. How to solve this? 
>>
>>  GET Messages   >>> Content
>>  GET Messages   >>> Content
>> 12:49:35.091 [ClusterSystem-akka.actor.default-dispatcher-3] DEBUG 
>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>> [ActorSelectionMessage(java.lang.String)] from 
>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>> [3072]
>> 12:49:35.092 [ClusterSystem-akka.actor.default-dispatcher-3] DEBUG 
>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>> [ActorSelectionMessage(java.lang.String)] from 
>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>> [3072]
>> 12:49:35.092 [ClusterSystem-akka.actor.default-dispatcher-3] DEBUG 
>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>> [ActorSelectionMessage(java.lang.String)] from 
>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>> [3072]
>> 12:49:35.092 [ClusterSystem-akka.actor.default-dispatcher-3] INFO 
>>  a.r.RemoteActorRefProvider$RemoteDeadLetterActorRef - Message 
>> [java.lang.String] from 
>> Actor[akka://ClusterSystem/user/master_1#-495216506] to 
>> Actor[akka://ClusterSystem/deadLetters] was not delivered. [1] dead letters 
>> encountered. This logging can be turned off or adjusted with configuration 
>> settings 'akka.log-dead-letters' and 
>> 'akka.log-dead-letters-during-shutdown'.
>> 12:49:35.093 [ClusterSystem-akka.actor.default-dispatcher-3] INFO 
>>  a.r.RemoteActorRefProvider$RemoteDeadLetterActorRef - Message 
>> [java.lang.String] from 
>> Actor[akka://ClusterSystem/user/master_1#-495216506] to 
>> Actor[akka://ClusterSystem/deadLetters] was not delivered. [2] dead letters 
>> encountered. This logging can be turned off or adjusted with configuration 
>> settings 'akka.log-dead-letters' and 
>> 'akka.log-dead-letters-during-shutdown'.
>> 12:49:35.093 [ClusterSystem-akka.actor.default-dispatcher-2] DEBUG 
>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>> [ActorSelectionMessage(java.lang.String)] from 
>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>> [3072]
>> 12:49:35.095 [ClusterSystem-akka.actor.default-dispatcher-2] DEBUG 
>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>> [ActorSelectionMessage(java.lang.String)] from 
>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>> [3072]
>> 12:49:35.097 [ClusterSystem-akka.actor.default-dispatcher-2] DEBUG 
>> a.r.a.Association(akka://ClusterSystem) - Dropping message 
>> [ActorSelectionMessage(java.lang.String)] from 
>> [Actor[akka://ClusterSystem/user/master_1#-495216506]] to [Actor[akka://
>> ClusterSystem@127.0.0.1:2551/]] due to overflow of send queue, size 
>> [3072]
>>
>> How can 
>>
>> On Wednesday, 24 May 2017 00:05:42 UTC+5:30, chaitanya wrote:
>>>
>>> Hi guys,'
>>> I am a newbie to akka cluster  and  i have created a sample program. I 
>>> am using producer consumer pattern. My producer sends messages to consumer 
>>> which are 2 seed nodes.
>>> The program works fine when no of messages are less like in thousands 
>>> but the program seems to seize when i send huge no of messages to seed 
>>> nodes. 
>>>
>>> I have implemented artery remoting and for this i refer to  
>>> http://doc.akka.io/docs/akka/2.5/java/remoting-artery.html
>>>
>>> Please find project in attached zip. Can anyone please help me out with 
>>> this 
>>>
>>> -- 
>> >> 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

Re: [akka-user] ANNOUNCE: New Akka documentation, website and Akka 2.5.2 released

2017-05-25 Thread Konrad Malawski

Hi Lee,
RSS works for me, do you use this feed: http://akka.io/rss.xml ?

-- 
Konrad `ktoso` Malawski
Akka  @ Lightbend 

On 25 May 2017 at 10:06:00, Lee_T (lee.tibb...@gmail.com) wrote:


New blog website looks spiffy.  RSS feed appears broken.
Is it intended to work?  It would be a pity to lose it because
of the transition.

Thanks,

Lee

--
>> 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

-- 
>>  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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Trouble getting Cluster with Consistent Hashing Router configured in a Docker environment to work reliably

2017-05-25 Thread Vishnu Vardhan


Hi,

I am trying to create a cluster, that uses a consistent hashing router, 
running in a docker container. I am unable to get this to behave 
consistently.

Please see my config and code attached. 

My errors vary from
1. Slave actor systems not joining and timing out (i have increased timers 
to adjust)
2. one of the routee workers consistently not being able to send msgs to 
the router, but other routes on the same host are able to 

I have the two application.conf files attached - one for the master, and 
the other for the slave.

Since this is a cluster singleton, running in docker, i am passing 
variables in via shell variables and initializing some parts of the cluster 
in code. 

Please see my code attached. Would appreciate any guidance in how to debug.

I suspect, and tried to address the following

1. cluster timers because this is a blocking compute job 
   - i have created specialized executors with dedicated threads to 
address this, I have also just disabled the blocking call to test whats 
going on
   - tried to create specialized dispatchers for the cluster

One of the error messages on the slave that has the failing routee that i 
am unable to understand (and could be contributing is)

 56 05:42:04.434UTC DEBUG ystem/system/cluster/core/daemon: now supervising 
Actor[akka://system/system/cluster/core/daemon/joinSeedNodeProcess-1#882767345]

119 05:43:02.560UTC DEBUG lActorRefProvider(akka://system): resolve of path 
sequence [/system/cluster/core/daemon/joinSeedNodeProcess-1#882767345] 
failed



Master and slave init code is below - 


Master Init 

  // validate and setup config file

val portNumber = ConfigFactory.load().getInt(
"Master.akka.remote.artery.canonical.port")

val (hostName,bindHostname) = 

  if(sys.env.get("HOST_IP_ADDR").isDefined) 

(sys.env.get("HOST_IP_ADDR"
).get,InetAddress.getLocalHost.getHostAddress)

  else


(InetAddress.getLocalHost.getHostAddress,InetAddress.getLocalHost.getHostAddress)



val myConfig = ConfigFactory.parseString(

  String.format("""

Master.akka.remote.artery.canonical.hostname = "%s"

Master.akka.remote.artery.bind.hostname = "%s"

Master.akka.remote.artery.bind.port = 25521

Master.akka.cluster.seed-nodes = ["akka://system@%s:%s"]

""".stripMargin, hostName, bindHostname, hostName, portNumber
.toString()))



// 
http://doc.akka.io/docs/akka/current/general/configuration.html#Reading_configuration_from_a_custom_location

val config = ConfigFactory.load(myConfig
.withFallback(ConfigFactory.load()))



if (config.getStringList("akka.cluster.seed-nodes").size() > 1) {

  log.error("too many seed nodes in config file")

  System.exit(1)

}



println("Cosbench_ng master is UP at: akka://system@%s:%d".format(
hostName,portNumber))

println("Status in log directory: /tmp/cosbench_ng")



implicit val asystem = ActorSystem("system",config.getConfig("Master"
).withFallback(config))

implicit val timeout = Timeout(5.seconds)

  

val cluster = Cluster.get(asystem)

val flowControlActor = asystem.actorOf(FlowControlActor.props)





// create the flow that does the work

// global singleton actor that routes messages to multiple workers

// and collates results into a statistics queue  


asystem.actorOf(ClusterSingletonManager.props(

  singletonProps = MyRouter.props(),

  terminationMessage = PoisonPill,

  settings = ClusterSingletonManagerSettings(asystem).withRole("router"
)),

  name = "myRouter")





Slave init code --



 

  val (hostName,bindHostname) = 

 if(sys.env.get("HOST_IP_ADDR").isDefined) 

(sys.env.get("HOST_IP_ADDR"
).get,InetAddress.getLocalHost.getHostAddress)

 else


(InetAddress.getLocalHost.getHostAddress,InetAddress.getLocalHost.getHostAddress)



  // setup configuration

  val myConfig = ConfigFactory.parseString(

  String.format("""

Slave.akka.remote.artery.canonical.hostname = "%s"

Slave.akka.remote.artery.bind.hostname = "%s"

Slave.akka.cluster.seed-nodes = ["%s"]

""".stripMargin, hostName, bindHostname, cmd.get.master.get))



  println("Connecting to master: " + cmd.get.master.get)



  // 
http://doc.akka.io/docs/akka/current/general/configuration.html#Reading_configuration_from_a_custom_location

  val config = ConfigFactory.load( myConfig.withFallback( 
ConfigFactory.load() ) )


  // actors in this actor system are created remotely

  implicit val system = ActorSystem("system",config.getConfig("Slave"
).withFallback(config))

  

  val cluster = Cluster.get(system)  

  println("Slave is up at: " + cluster.selfUniqueAddress.address)





-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html

Re: [akka-user] ANNOUNCE: New Akka documentation, website and Akka 2.5.2 released

2017-05-25 Thread Lee_T


New blog website looks spiffy.  RSS feed appears broken.
Is it intended to work?  It would be a pity to lose it because
of the transition.

Thanks,

Lee

-- 
>>  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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Akka stream - Source of http response.

[akka-user] ANNOUNCE: New documentation theme and Akka HTTP 10.0.7 Released

Re: [akka-user] Akka Distributed Data Sample thowing OversizedPayloadException

[akka-user] Dispatcher configuration ?

Re: [akka-user] Akka Distributed Data Sample thowing OversizedPayloadException

[akka-user] cluster heartbeat delay

[akka-user] AKKA cluster heartbeat delay

Re: [akka-user] Re: Issue in Sending messages through akka cluster.

Re: [akka-user] Re: Issue in Sending messages through akka cluster.

Re: [akka-user] ANNOUNCE: New Akka documentation, website and Akka 2.5.2 released

[akka-user] Trouble getting Cluster with Consistent Hashing Router configured in a Docker environment to work reliably

Re: [akka-user] ANNOUNCE: New Akka documentation, website and Akka 2.5.2 released

12 matches

Site Navigation

Mail list logo

Footer information