Hi Rohit,

you mention a “potential leak” and “getting similar stack traces”. How and why 
exactly are these stack traces emitted? Due to a crash?

One thing that comes to mind are thread pool sizes: if you have really big 
pools configured, then you will see lots of file descriptors being used (two 
per thread on JVMs I looked at).

Another thing: have you made certain that you don’t create ActorSystems other 
than during application start-up? (we had reports of this kind where someone 
had used `def` where `val` was meant—it happens to the best!)

In any case, we would need to see the thread dump and the akka config from a 
failing system in order to be certain.

Regards,

Roland

13 mar 2014 kl. 01:43 skrev Rohit Gupta <[email protected]>:

> We are using Akka 2.1.4 in our app in production. Its a distributed 
> application and there is an actor system on each node.
> There is a potential file descriptor leak that is killing the process on 
> nodes.
> 
> While trying to reproduce the same issue in dev environment, I saw that the 
> when the actor system starts on the nodes. The # of pipes for this process is 
> ~ 200 [ & total FDs around 600], after hitting this node with load over a 
> period of time, the # of pipes go up, and they don't come down even when no 
> more requests are being sent to the system. 
> Although, I am not able to conclude if its load that's causing the # of pipes 
> to rise.
> 
> This may be a potential cause of the leak, but I am not very sure as I don't 
> have access to production nodes.
> 
> We were getting the similar stack trace to what is posted in 
> https://groups.google.com/forum/#!msg/akka-user/tLBZu5Sr0vU/k7emeQYdvzQJ
> So we went ahead and upgraded the Akka version to 2.2.3, but it didn't seem 
> to help.
> 
> 1) While upgrading, we just upgraded the library, dependencies and 
> configurations and not the deprecated akka apis as it would lead to too many 
> changes in our stable application. Should that be fine?
> 2) Any suggestions to what might be causing this problem and how should this 
> be tackled?
> 
> -Rohit
> 
> -- 
> >>>>>>>>>> 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 [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/d/optout.



Dr. Roland Kuhn
Akka Tech Lead
Typesafe – Reactive apps on the JVM.
twitter: @rolandkuhn


-- 
>>>>>>>>>>      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 [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/d/optout.

Reply via email to