Open MartinPontius opened 2 years ago
My suggestion would be to not necessarily require more connections to postgres (though that could also be increased), but to implement a queue where a client can be put on hold until a DB connection becomes available again without having to return a 500 error. Perhaps this could also be implemented higher up, maybe even above the pygeoapi provider level?
Update: this problem seems constantly to occur for simple/single requests after the service has been running for a while.
When multiple (parallel) coverage requests are coming in the server returns error code 500 as it fails with
Possibly multiple database connections are opened but not closed again or postgres restricts the number of connections per default too much for our use case.