Actually, I just realized that the problem is in MixMetricsSelector. Until yesterday, I was using this two Azure instances with 1,5GB RAM and MixMetricsSelector distributed jobs properly. However, after I changed to 3,7GB RAM instances, it could never distribute job to other job, even if the first node was heavily used and I could even reach OutOfMemoryException. After I changed to HeapMetricsSelector it works fine again. I thought MixMetricsSelector will check heap, cpu and load and find the node with the maximum available capacity to process the task, but for some reason it doesn't work as I was expecting.
Zoran On Thursday, 5 December 2013 12:04:23 UTC-8, Zoran Jeremic wrote: > > Hi, > > I created application following the tutorial > http://doc.akka.io/docs/akka/snapshot/java/cluster-usage.html > I have 2 nodes having 1 front-end and 1 back-end on each. Backend is > initiated as AdaptiveLoadBalancingPool and it is subscribed to memberUp > events. > I implemented registration of backends through the processing of > CurrentClusterState and MemberUp messages in the same way as described in > Worker Dial-in Example of the tutorial. However, the problem is that I end > up with 12 registered backends on each node. > > Do you have any idea what could be the problem there? > > Thanks, > Zoran > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/groups/opt_out.
