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.
