[4.3] temporarily increase query timeout during database warmup #480
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Nominatim 4.3 introduced a new mechanism for setting query timeouts osm-search/Nominatim#3172
For a large import like planet, this resulted in timeouts while running the warmup queries:
To overcome this, I am temporarily setting the query timeout to 600 seconds while running the warmup command and revert back to 10 seconds after it completes.
A further improvement idea would be to create different env variables for those timeouts (something like
DOCKER_NOMINATIM_QUERY_TIMEOUT
instead ofNOMINATIM_QUERY_TIMEOUT
) to allow users to specify different timeouts for their use-cases.Fixes #478