Guido, I agree with your advice.
I just wanted to mention the wrong conf property as additional info.
/Patrik
mån 24 aug 2015 kl. 17:23 skrev Guido Medina :
> And more information about the application itself to see memory usage
> patterns.
>
>
> On Monday, August 24, 2015 at 4:22:10 PM UTC+1, Gui
And more information about the application itself to see memory usage
patterns.
On Monday, August 24, 2015 at 4:22:10 PM UTC+1, Guido Medina wrote:
>
> Hi Patrik,
>
> I'm quite sure his problem has anything to do with Akka but lack of proper
> JVM parameters, that 32 seconds pause shown in his l
Hi Patrik,
I'm quite sure his problem has anything to do with Akka but lack of proper
JVM parameters, that 32 seconds pause shown in his logs would be enough to
cause nodes de-association and connection failures/timeouts of Akka remote
(without mentioning Akka cluster and other extensions) henc
Note that there is no: akka.cluster.transport-failure-detector
you probably mean: akka.remote.transport-failure-detector
The Disassociated might be triggered by that failure detector and you can
try to increase
akka.remote.transport-failure-detector.acceptable-heartbeat-pause
/Patrik
On Fri, A
Try the JVM option -XX:+UseG1GC, assuming you are using at least JVM
7uLatest where latest should be 79 or 80. The new GC algorithm doesn't stop
world, it works more often and can make your application a bit slower (on a
very hyper micro-level) but GC will now be consistent.
On Friday, August 2
