-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check behavior of tile requests during database crash #170
Comments
Killing postgresql on direct connection results in immediate response:
|
Improvement in the mapnik error message have been submitted as a pull request: Also a possible segfault on crash has been submitted: |
Next stop: test with pgbouncer |
So, what happens with pgbouncer is highly dependent on pgbouncer configuration. The default can be overridden by using the For this reason we'd better implement a tiler-specific timeout for the database connection, |
Desired behavior on database crash is whatever can result in a relatively "quick" response.
Could be an error on timeout or crash detection.
There could be some attempts at reconnecting too, maybe, but in that case there should be an upper limit on the time of attempting that.
For the reconnecting mapnik attempts,
See mapnik/mapnik#499 for the crash detection.
For a generic timeout, see #169
JIRA REF: https://cartodb.atlassian.net/browse/CDB-1935
The text was updated successfully, but these errors were encountered: