-
Notifications
You must be signed in to change notification settings - Fork 80
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
Connection closed/aborted errors for requests for vector tiles that take a long time to generate #56
Comments
Are you proxying tessera through a different web server (e.g. Apache or Nginx)? tessera shouldn't time out, so I suspect that any timeouts you're experiencing are either due to the reverse proxy layer or the client. The log line you included is symptomatic of Express (the underlying HTTP server) acknowledging that the client disconnected. You can confirm this by running If you're doing batch generation of vector tiles, you may be better off with |
I think it might be going through Apache. What should I change to make apache work?
I'm using Hyper HTTP client in Rust. I've set the timeout on the HTTP request to 24 hours, so I'm stumped as to what is wrong.
I initially looked at them, but they only support a few "output formats", and I wanted to store vector tiles in a stepped directory (tilecache layout). Additionally, I want to "expire" some vectortiles, by downloading a list of URLs and saving them, rather than download everything again. |
I have time to look at this again.
I'm not using apache. I'm going direct to
Here is some output:
And the corresponding line in tessera's stdout:
Any ideas? |
(Sorry for the delay.) It definitely looks like there's a 2 minute timeout somewhere, the big question being where. It might be I don't see anything in
|
The query is continue to be run after the HTTP connection is closed:
|
For the record, I've switched to this approach. It solves my problem. I didn't know However it would still be good to have a proper fix inside |
I have a tmsource project and I'm using tessera to serve the vector tiles from it. This tmsource project uses a lot of PostgreSQL queries that take a long time to run. And when my http client requests a vector tile from tessera it can fail with a http connection aborted / connection closed error. The tessera output shows:
GET /pbfs/live//14/7794/3493.pbf - - ms - -
.Is there anyway to make tessera not timeout, and to wait a long time before "giving up". This way, I'd get my vector tiles, even if they take a long time.
In the long run, we need to improve our SQL queries, but we're curring using tessera to generate vector tiles in a batch manner, so waiting a long time is not a big problem.
The text was updated successfully, but these errors were encountered: