Reset queue delay to 0 seconds #1
Description
Note to my future self.
I've just updated the queue processing delay to 60 seconds in the Cloudflare dashboard. The default value is 0. Increasing the delay should hopefully help ensure that the changeset has already been fetched by the Django backend before the Cloudflare worker POSTs to the tag-changes endpoint (if it does this before the backend has fetched the changeset, it 404's and discards the tag changes data). I'm not sure yet if 60 seconds is enough or if it'll need to be increased further.
In a better world, the Django backend would gracefully handle receiving tag changes for a changeset that it didn't know existed yet. Maybe the Cloudflare Worker could even be refactored to push the changeset adiff itself to the backend, and be the sole source telling the backend when new changesets are created (no need for it to poll the replication server).
When that better world arrives, there will be no sense in keeping this artificial delay in the queue processing latency. So don't forget to reset the value back to zero.
See also OSMCha/osmcha-deploy#58, another mitigation for this issue.