You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I'm experiencing the occasional timeout on the server I fetch the changes from ( Unable to read the state from the server.)
Usage is:
osmosis --read-replication-interval workingDirectory=rri --simplify-change --write-xml-change file=changes.osc
and only if that succeeds the osm2pgsql starts
In the ideal world I would just want to restart it on failure so it can try again, but I do not know the risk of missing one update in some edgecase.
I guess it boils down to not being able to crash in any way after updating the state.txt
The text was updated successfully, but these errors were encountered:
doskabouter
changed the title
[Question]
[Question] Is it always safe to restart osmosis when it crashes?
May 16, 2022
Currently I'm experiencing the occasional timeout on the server I fetch the changes from ( Unable to read the state from the server.)
Usage is:
osmosis --read-replication-interval workingDirectory=rri --simplify-change --write-xml-change file=changes.osc
and only if that succeeds the osm2pgsql starts
In the ideal world I would just want to restart it on failure so it can try again, but I do not know the risk of missing one update in some edgecase.
I guess it boils down to not being able to crash in any way after updating the state.txt
The text was updated successfully, but these errors were encountered: