Hi,
I've read it in the past, but was hoping it's not accurate (I'm already
using an asynchronous logger as the backend).
It basically says that no - there is no way to achieve what I want with
Akka Logging, because while an asynchronous backend may help, the messages
still go through some
That sounds related, but the problem in the case of logging is that (as far
as I know) it runs on the default dispatcher and cannot be reconfigured.
And anyway, I'm thinking of a case where regardless of dispatcher, there's
just too many messages and we cannot possibly manage to write them all.
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 декабря
Hi Adam,
I think what you are describing is covered in the logging docs:
http://doc.akka.io/docs/akka/2.4.1/scala/logging.html#Loggers
and http://doc.akka.io/docs/akka/2.4.1/java/logging.html#Loggers
It could probably be more clear though, but the system behaving bad with
high logging load
