_ about headway HOT 6 CLOSED

I get the following error in the docker-compose log:

headwaymaps-valhalla_init-1 | http://: Invalid host name.
headwaymaps-valhalla_init-1 | xz: (stdin): File format not recognized

The container named headwaymaps-valhalla_init corresponds to services/valhalla/init.sh

Looking at that file, it seems likely that you're trying to download $VALHALLA_ARTIFACT_URL. But that shouldn't happen if you've built all the artifacts as the instructions describe.

I do have Earthly installed and running, but when I try to run the docker-compose,

Did you run the build? Something like:

earthly -P +build --area=Amsterdam

Did it succeed?

from headway.

For context, broadly speaking, there are two parts to this project.

1. The part that compiles all the mapping data (e.g. earthly +build)
2. The services that hosts the compiled mapping data. (e.g. docker compose up)

We cant expect the second part to work without the first part being completed. Your original report was an error with starting docker compose, but first you'll have to figure out why building the data failed.

+pelias-import failed | Elasticsearch did not come up, check configuration

Any thoughts why elasticsearch didn't come up?

For very large builds (planet scale) I've had issues with what I suspect might actually be a timeout:
pelias/docker#217 (comment)

I haven't run into that issue on smaller builds, but I suppose that could depend on your machine setup. Adjusting your esclient timeout for the build portion as I did in the link could be one thing you try.

from headway.

NY+PA is a big extract, so I'd suspect memory pressure as a potential reason elasticsearch might not come up during import. Try setting your buildkit parallelism to 1 according to FULL_PLANET.md. Just a hunch :)

from headway.

Looks like I may not have documented buildkit parallelism, but you can follow this documentation to set up an earthly config file. Glancing through the docs it looks like running earthly config global.buildkit_max_parallelism 1 might also work.

from headway.

It's pretty easy to OOM while working with large extracts or planet builds if you allow earthly to run many tasks in parallel. I've done it even with 128gb of RAM. I don't think it's a timeout issue but that's certainly possible too. Super curious to see if the buildkit parallelism tweak fixes it. Failing that, another good data point would be building a small area like Amsterdam.

from headway.

It's impossible to diagnose this without build logs.

from headway.