[erlang-questions] Lager dropping messages

[Jesper Louis Andersen]

One thing to be aware of here: When your Erlang instance boots, it logs
quite much. Often so much that this overload protection will trigger. If
your node() is dying early on in the boot phase, consider bumping this
count to 3000 or so.

On Mon, Sep 11, 2017 at 7:05 PM Luke Bakken <lbakken@REDACTED> wrote:

> Hi Frank,
>
> I think this is what you're looking for:
> https://github.com/erlang-lager/lager#overload-protection
>
> On Mon, Sep 11, 2017 at 8:38 AM, Frank Muller
> <frank.muller.erl@REDACTED> wrote:
> > Hi guys,
> >
> > I’m seeing this annoying warning in my logs:
> > [warning] lager_error_logger_h dropped 107 messages in the last second
> that
> > exceeded the limit of 50 messages/sec.
> >
> > How can i set Lager (I’m using lager v2 from trunk) and increase this
> limit
> > of 50msg/sec (ex. set it 300)?
> >
> >
> > Thank you.
> > /Frank
> > _______________________________________________
> > erlang-questions mailing list
> > erlang-questions@REDACTED
> > http://erlang.org/mailman/listinfo/erlang-questions
> >
>
>
>
> --
> Staff Software Engineer
> Pivotal / RabbitMQ
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20170911/4f3aea61/attachment.htm>