Hello! I saw the same problem when default dispatcher was overloaded by a lot of small tasks that was created via map/flatMap/etc operations on Future's. I fixed my problem by moving away heavy batch processing and operations on futures to dedicated dispatcher.
Maxim воскресенье, 13 декабря 2015 г., 19:15:36 UTC+3 пользователь Adam написал: > > Hi, > > I sometimes see this issue where I want to switch logs to DEBUG, but due > to the large number of messages the JVM will crash on OutOfMemory which > turns out to be due to the accumulation of logging events. > Most logging frameworks have the ability to drop messages beyond a certain > number and so do Akka unbounded mailboxes. > > Is there a way to achieve this with Akka logging as well? > The behavior of the non blocking unbounded mailbox is what I have in mind > (logging frameworks usually add a warning of some kind telling you that > messages are being dropped, but I can manage without this for now). > > Alternatively, I could just using my logger directly. > It's asynchronous anyway. The only issue with that is that I find the > extra MDC data of actor path very useful when looking at piles of DEBUG > logs. > It makes zeroing in on a single transaction very simple. > -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
