[erlang-questions] error_logger and the perils of asynchronicity

[Caoyuan]

On Sat, May 16, 2009 at 8:10 PM, Steve Davis
<steven.charles.davis@REDACTED> wrote:
>
>
> On May 14, 5:55 pm, Oscar Hellström <os...@REDACTED>
> wrote:
>> Ah, but in this case, in the event of a system failure (which results in
>> the VM crashing from running out of memory) we still wouldn't know what
>> should have been logged.
>>
>
> OK, so let's assume you have a complex application that generates lot
> of log messages and you absolutely cannot affort to lose. What about
> logging out to a message queue (e.g. Rabbit)?

There is a case study:
http://blogtrader.net/dcaoyuan/entry/a_case_study_of_scalable

and a solution:
http://blogtrader.net/dcaoyuan/entry/async_or_sync_log_in

> /s
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>