lallinger-tech

> Hi @lallinger-arbeit > Thanks for this PR, I have written some comments. > Once they are done, you need to sign the commit in order to resolve the DCO....

Could it be, that multiple endpoints worsen this? a fresh install with 10 endpoints already throws this error.. @liranmauda @jeniawhite

> @lallinger-arbeit this error is thrown by PostgreSQL when exceeding the `max_connections` which is the maximum number of concurrent connections the DB is configured to handle (see [here](https://www.postgresql.org/docs/12/runtime-config-connection.html)). We are...

i'll try to reproduce it, but probably won't have time to do it until end of next week..

@liranmauda are you tracking the remaining connections issue here or somewhere else? if you track it somewhere else this can be closed

@guymguym Currently the logs of the mongodb vanished.. i will try to reproduce them and look for a seg fault. Nevertheless the updated image does not work and only outputs:...

@guymguym just reproduced it with the normal MongoDB image and catched the logs. It is a segmentation fault which seems to be linked to "func_stats" see here: ``` 2020-12-07T07:25:57.126+0000 I...

with `mongo:3.6.21` it looks way better, 30k events so far and no seg fault! thanks @guymguym !

After testing further with hit a barrier at 60k events. Everything works fine until you try to visualize the events via the UI. This then renders the noobaa-db pod unusable...

@jeniawhite i just tested it with a fresh noobaa instance and unfortunately it does not seem to improve the performance and the same problems as seen before persist..