openstreetmap-tile-server icon indicating copy to clipboard operation
openstreetmap-tile-server copied to clipboard

Published 20 hours ago • verified publisher icon Overv

Automatic updates: handling of failures

Open soberdor opened this issue 4 years ago • 1 comments

Size and memory consumption of update packages vary greatly. While the preset 3600s-limit (configuration.txt) works well most of the time, some of the updates run out of memory (in my case 18GB allotted to Docker, using a 32GB swap on an SSD for a Europe-only server). Upon failing, the same update is attempted over and over again.

Suggestion: upon failure during osm2pgsql ("killed"), fall back to smaller chunks (e.g. 50%)

Another issue related to failure handling is, that if the container is stopped for any reason during an update, "state.txt" is left unchanged and therefore reflects the interrupted update as complete. Upon restart the subsequent update is started automatically, with unclear results (at best an incompletely updated database).

Suggestion: update "state.txt" only after successful import process

soberdor avatar May 20 '20 11:05 soberdor

Sorry for the delay, feel free to open a PR :)

galewis2 avatar Feb 17 '22 14:02 galewis2