[Geoserver-devel] [JIRA] (GEOS-7141) Document "Tile locking mechanism" on "Cached Defaults" page

Mike Pumphrey created an issue

GeoServer / TaskGEOS-7141

Document “Tile locking mechanism” on “Cached Defaults” page

Issue Type:

TaskTask

Affects Versions:

2.7.2

Assignee:

Kevin Smith

Components:

Documentation

Created:

04/Aug/15 11:43 PM

Fix Versions:

2.7.3

Priority:

LowLow

Reporter:

Mike Pumphrey

This page is lacking info about the “Tile locking mechanism” setting:

http://docs.geoserver.org/latest/en/user/webadmin/tilecache/defaults.html

Kevin, Ben described it as thus:

“”"
GeoWebCache needs to keep track of what file operations are currently ongoing, so that two simultaneous operations do not interfere with one another. By default, GeoWebCache uses in-memory locks since it knows what it is doing. However, if there are two GeoWebCache instances sharing a single on-disk cache, they won’t know what the other is doing and there is the risk of a collision.

The alternative, NIO locking, uses the filesystem’s own locking to prevent simultaneous access. This is a little bit slower, but ensures safety with greater than one GeoWebCache instance.
“”"

If this looks good to you, feel free to reassign and I’ll add it in.

Add Comment

Add Comment

This message was sent by Atlassian JIRA (v6.5-OD-08-001#65007-sha1:1fc9846)

Atlassian logo