I'm using akka cluster sharding to build for *a long connection streaming
*distributed
calculation engine.
It's driven by request, basically for each request, there will be one
entity actor started for calculation of that request, and this is a
streaming request, which means the calculation
Thank you guys for your information.
On Friday, 19 May 2017 18:46:56 UTC+8, Evgeny Shepelyuk wrote:
>
> Hello,
>
> We're using ELK for our Docker based services and currently it's quite
> useful for collecting and analyzing logs.
> There's another option https://www.graylog.org - it works very
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]
Hi,
I'm using tcp for outgoing connection in akka streams.
Tcp().outgoingConnection(...)
if the target connection drops you can see something like this in debug logs
[DEBUG] [05/23/2017 14:08:41.968] [default-akka.actor.default-dispatcher-5]
[akka://default/system/IO-TCP/selectors/$a/0]
I can't see that error in the log messages you included, but in general:
http://doc.akka.io/docs/akka/2.5/scala/distributed-data.html#Limitations
You can sometimes split one data entry into several, e.g. instead of having
one huge ORSet you can use 10 ORSet at the top level and pick the right one
