Hello Jukka,
Thank you for attempting to reproduce the problem. Interesting that I
can consistently reproduce the issue on my machine - perhaps some part
of my configuration is causing the issue. As I said before, I can easily
get around this issue by using the REST interface for mass truncation,
which does work. Just wanted to be sure this was documented if it was
indeed a bug related to the geoserver admin interface.
I suppose since this isn't completely reproducible by others (or only
occurs part of the time, given the behavior you describe with
truncates), I will hold off on opening a bug report.
Thanks again,
Trey
On 09/26/2018 06:31 AM, Rahkonen Jukka (MML) wrote:
Hi,
I made a simple test with Geoserver 2.14-snapshot and topp:states layer on
Windows. I seeded the layer for zoom levels 0-9 and checked that there were
directories and tiles. Then I pressed the Empty button and all the directories
and tiles were removed. Only the empty main directory
\data_dir\gwc\topp_states remained.
That said I have also experienced unreliable truncates before both on Windows and Linux. Truncate
did not delete all the tiles but some old ones remained here and there. Because the server was in
use all the time it was hard to check if truncate was successful and we found the issue due to
feedback from the customers. We changed the workflow from "truncate - let new tiles appear
when they are requested" to "reseed all zoom levels" which is heavier but reliable.
I never managed to catch logs from the error or reproduce it in a reliable way.
-Jukka Rahkonen-
-----Alkuperäinen viesti-----
Lähettäjä: Trey Stafford [mailto:[email protected]]
Lähetetty: 25. syyskuuta 2018 19:56
Vastaanottaja: GeoServer Mailing List List
<[email protected]>
Aihe: Re: [Geoserver-users] Emptying tile layer cache
With respect to opening a ticket for this issue - I see that I should have the
problem confirmed by a third party before submitting an official bug report.
Would someone be willing to verify that what I am experiencing is in fact a
bug? Reproducing should be simple:
1. Create a layer and configure it to utilize geowebcache.
2. Seed the cache
3. Attempt to empty the cache with the "Empty" button associated with the layer in the admin
interface (under the "Tile Caching" section on the left hand side, click the "Tile
Layers" link). After clicking and accepting the confirmation dialogue, the layer should now show 0.0B of
disk space used for the cache.
4. Confirm that the cache actually still exists. Navigate to the geowebcache data directory
and observe that the layer's tile cache is still present (the directory should be named
<WORKSPACE>_<LAYER_NAME>).
On 09/25/2018 10:44 AM, Trey Stafford wrote:
All,
I have had some success with clearing a layer's cache this morning. By
using the 'masstruncate' REST endpoint to geowebcache, I can
successfully clear the cache for the specified layer. Doing so removes
the directory containing the previously generated tiles for the layer,
and the geoserver admin interface correctly shows 0.0 B for disk usage.
I still haven't had any luck getting the 'Empty' button in the admin
interface to work, despite it showing 0.0B of disk space used after
clicking it (even refreshing the page shows 0.0 B of disk usage, even
though a directory listing shows otherwise). I suspect this is a bug,
so I'll be opening a bug report for this issue.
Thanks again,
Trey
On 09/24/2018 11:59 AM, Trey Stafford wrote:
Hello,
I have encountered what I believe to be some unexpected behavior with
tile layers cached by geoserver's internal geowebcache implementation.
In the "Tile Layers" menu of the Geoserver admin interface, each
layer is listed along with information about how much disk space is
used for tile caching. There's an option to "Empty" the cache,
removing all cached tiles for the given layer. After selecting this
option, the disk usage for the layer is given as 0.0 B.
However, checking the geowebcache data directory shows quite the
opposite: disk usage actually increases by about 1MB after this
operation, and all cached tiles still appear to be present. I can
remove the source data from the layer (image mosaic data store) and
still make gwc requests that serve the tiles that had been previously
cached when the source data was present.
There does not appear to be anything in the logs that would suggest
an error is occurring, so perhaps I am misunderstanding what the
"Empty" option actually does. I have also attempted to use gwc
"truncate" to remove cached tiles without success.
I have experienced the above described behavior using Geoserver
versions 2.10.0, 2.13.2, and 2.14.0 on a Debian 9 host. The layer I
have been testing is an image mosaic with the TIME dimension enabled.
If anyone has any suggestions for why I am experiencing this
behavior, or how I might properly go about emptying the cache, I
would greatly appreciate it! The data in our image mosaic is
occasionally updated (there's an image associated with each day of
the year, sometimes a date is updated when further processing is
complete), so I need to invalidate the existing cache and re-seed
with the new data.
Thanks in advance!
Trey
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting
to this list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-an
d-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
