Cache invalidation problems when database content changes

[mkovac-conductive]

I would like to know what is the recommended way to handle tile cache invalidation when database content changes? Currently I need to restart martin server to get latest data on my Mapbox page.

My setup:

Frontend: React (with Mapbox)
Tileserver: Martin
Database: PostgreSQL

Thanks!

[CommanderStorm]

Currently, restarting is the only option.

While this should be pretty quick, this is not ideal (we know).
The current draft of an API route for this would be a massive performance hit and has thus not been merged.

See

• Add /refresh to update sources and some configurations #1179

[CommanderStorm]

I think we should track this in #288 instead, given that said issue already has a discussion about how this can/should be implemented

=> Closing as a duplicate of #288 ^^

[nyurik]

I keep wondering if we should kill the tile cache for now - it is more of a nuicance than help - response caching can be done much better at the load balancer or reverse proxy level (e.g. GCP Load balancer / Varnish / Nginx / ...).

The only real reason for cache (why i initially introduced it) - was to cache pmtiles directory structure so it doesn't need to be refetched for each tile