The dwd.de website had a prolonged intermittent outage this week. Even though the open data server had no availability issues, this led to our data becoming stales because we
a) load the station list when starting the worker, and
b) frequently restart the worker in a cronjob on the production server.
We should cache this station list on the file system and fall back to that if dwd.de is unavailable. We could also consider disabling the cronjob as the memory issues it was a workaround for are now gone. I'm leaning towards leaving that one active though, as it's still a nice failsafe against unexpected hiccups during processing (at least once we added station list caching).
jdemaeyer
commented
6 months ago
The dwd.de website had a prolonged intermittent outage this week. Even though the open data server had no availability issues, this led to our data becoming stales because we
a) load the station list when starting the worker, and b) frequently restart the worker in a cronjob on the production server.
We should cache this station list on the file system and fall back to that if dwd.de is unavailable. We could also consider disabling the cronjob as the memory issues it was a workaround for are now gone. I'm leaning towards leaving that one active though, as it's still a nice failsafe against unexpected hiccups during processing (at least once we added station list caching).