Skip to content

Log can be flooded by warning messages #2218

Closed
@locker

Description

@locker

For instance, when tarantool hits the limit on open files, the log is flooded with thousands messages like below, which makes it difficult to read the log.

2017-03-18 10:09:40.788 [19872] iproto sio.cc:251 !> SystemError accept, called on fd 13, aka 0.0.0.0:3301: Too many open files
2017-03-18 10:09:40.788 [19872] iproto sio.cc:251 !> SystemError accept, called on fd 13, aka 0.0.0.0:3301: Too many open files
2017-03-18 10:09:40.788 [19872] iproto sio.cc:251 !> SystemError accept, called on fd 13, aka 0.0.0.0:3301: Too many open files
2017-03-18 10:09:40.788 [19872] iproto sio.cc:251 !> SystemError accept, called on fd 13, aka 0.0.0.0:3301: Too many open files
2017-03-18 10:09:40.788 [19872] iproto sio.cc:251 !> SystemError accept, called on fd 13, aka 0.0.0.0:3301: Too many open files
2017-03-18 10:09:40.788 [19872] iproto sio.cc:251 !> SystemError accept, called on fd 13, aka 0.0.0.0:3301: Too many open files

We need to come up with a way of limiting the rate at which messages can be printed to the log.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions