Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tile Caching: Caching Defaults: Enabling/Disabling the option "direct integration with GeoServer WMS" reflects only after WMS pod restart #171

Open
rubankumars opened this issue Jan 11, 2024 · 2 comments

Comments

@rubankumars
Copy link

Steps to reproduce:

  • Try checking the option "Enable direct integration with GeoServer WMS" under Tile Caching, Caching Defaults for the very first time.
  • Under Layers select a layer and Check "Create a cached layer for this layer" under Tile Caching tab for the particular layer
  • Try to access the layer using the WMS endpoint from the browser
  • Check for a folder with the name similar to the layer name under cache directory/persistent volume mount in any of the pod where the cache volume is mounted (It might have not created)
  • Try deleting the WMS pod which automatically creates a new pod with the updated configurations.
  • Try to access the layer again and now you will notice a new folder gets created and the layers start to cache the tiles.

Possible Reason: The WMS spring microservice loads the configuration when it initially starts and not being refreshed for every configuration changes until it restarts or starts again.

@groldan
Copy link
Contributor

groldan commented Jan 13, 2024

Hi @rubankumars , thanks for reporting, you assessment seems correct. I've created a bug in the geoserver cloud project: geoserver/geoserver-cloud#411

@groldan
Copy link
Contributor

groldan commented Oct 14, 2024

Fixed for GeoServer Cloud 1.9-SNAPSHOT as of geoserver/geoserver-cloud#549

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants