8

Hi @Acmeno

I would not say that this is an issue per se, since connection accepted event is useful for debugging in many cases, and supressing these informational events may make troubleshooting a lot harder in production environment.

There’s a discussion about exactly this in SERVER-18339. In particular, this comment on the ticket is of interest: in most cases, a connection open event is not expected to be very very frequent, unless you have a lot of clients, or there is minimal connection reuse in the application code. The latter actually merits further examination, since creating a connection is a relatively expensive event. If you have a small number of application but a huge number of connection open events, your app may experience a higher than expected latency due to the way it creates connections.

All official drivers implements a connection pool that should keep this connection open message to a minimum in most cases.

Having said that, you can also pass the --quiet parameter into mongod to supress at least some of these messages. However be aware that this switch also supress other messages that may be important for troubleshooting.

Best regards
Kevin