[Geoserver-users] REST API Truncate vs. local delete

GeoServer provides GeoWebCache REST API that may be used to truncate existing cached tile folders ( http://docs.geoserver.org/stable/en/user/geowebcache/rest/seed.html ).

If I have a local access to the tile cache folders, is it ok to handle truncating by simply deleting some of the folders by using my own scripts instead of using REST API. In other words, can bypassing the REST API to clean tile cache have some unwanted side effects? Only potential thing that comes into my mind is GeoWebCache Disk Quota service ( http://docs.geoserver.org/stable/en/user/geowebcache/rest/diskquota.html ). For example, is there a possibility that some quota counter becomes out of sync if deletion is not done via REST API?

Best regards,

--
Ville Karppinen
ville.karppinen@anonymised.com

I recently deleted 15gb of cache manually as the truncate was taking a long time

To fix the quota size I did the following :-

  1. Turned off disk quota

  2. Deleted my local files

  3. Deleted the h2 database

  4. Turned back on disk quota

  5. a new h2 database was created and sizes were correct

Mark Ismail

Principal IT Officer

Tel: 0151 443 3021

Knowsley Council K Westmorland Road Huyton L36 9GL

Save time – use the IT Service Desk Self Serve Application