consider flushing tile cache of specific area to remove outdated rendered data

[matkoniecz]

Some areas, sadly quite large, are stuck with outdated rendering due to how tile expire cache works.

I know that https://github.com/openstreetmap/operations/issues/987 will solve it for new cases if enabled

I know that it will take relatively long time to refresh it, but it may be worth doing as otherwise invalid renderings may stay for relatively long. Maybe flush cache of the most populated western parts of the area, while keeping eastern parts with some rare invalid data?

Was discussed with @Firefishy - got directed here to keep things triaged and in issues

(hopefully I managed to keep balance between being too cryptic and giving a manual)

[tomhughes]

Which cache are you talking about? The render cache or the CDN cache?

[Firefishy]

I think we will wait until https://github.com/openstreetmap/operations/issues/987 is fully deployed before any cache invalidation.

[Firefishy]

The render cache or the CDN cache?

It is primarily a render cache issue.

[tomhughes]

There is a new carto release (https://github.com/openstreetmap/chef/issues/639) that I will likely deploy next weekend which will have the side effect of marking everything dirty.

[Firefishy]

With and New carto release pushed. All old tile are now marked dirty and the issue shouldn't repeat.

[matkoniecz]

Thanks for a fix! That was a really annoying problem

---

I also updated https://wiki.openstreetmap.org/wiki/Browser_cache#Exceptions

---

See https://github.com/openstreetmap/chef/commit/a7d7bb9186bcd1ce33483c4587b80c90bc03534b causes relations to trigger rerender per https://community.openstreetmap.org/t/topic/106281/5 for what fixed it