when db has too many connections weird errors happen.

[rdallman]

In gitlab by @rdallman on Jul 17, 2017, 14:13

@denismakogon alluded to this in #111

this is the case i keep running into:

fn-api-deployment-2750180546-h378w fn-api time="2017-07-17T21:09:03Z" level=error msg="App not found" action="server.handleRunnerRequest)-fm" app=yodawg call_id=01BN9642M407WTE00000000000 error="Error 1040: Too many connections" route="/hello"

which we should handle in the function that fronts the api (return 5xx instead). we also need to probably figure out how to make this stop across all the various backends, we would prefer for them to wait and then possibly get hit with a timeout instead of just failing.

[rdallman]

In gitlab by @rdallman on Jul 17, 2017, 15:28

mentioned in merge request !109

[rdallman]

In gitlab by @rdallman on Jul 17, 2017, 15:36

related #96

[rdallman]

In gitlab by @denismakogon on Jul 18, 2017, 06:26

More erros at #123

[rdallman]

In gitlab by @rdallman on Jul 18, 2017, 11:20

mentioned in issue #123

[rdallman]

@denismakogon do you still see this? I no longer get 'weird errors' since we are now properly masking non user friendly errors in the front end.

[rdallman]

we still need this we also need to probably figure out how to make this stop across all the various backends, we would prefer for them to wait and then possibly get hit with a timeout instead of just failing. but moving elsewhere.