search

planetfederal / geoserver-exts

Other
31 stars 40 forks source link

Clustering Event mode does not remove cached data #31

Open smithkm opened 10 years ago

smithkm commented 10 years ago

When the Cluster module is in event mode old data is being retained after notification of an update.

With two nodes sharing a JDBCConfig catalog, update a catalog entry (title of a feature type for instance) then check on the other node, after waiting for the sync delay set in cluster.properties and the title will not have updated. It will update eventually, on the order of minutes.

The ResourcePool which is doing the caching is being notified and is apparently cleaning up its cache in response. There must be additional caching going on somewhere.

jdeolive commented 10 years ago

The jdbcconfig facades cache objects internally to save trips to the database... could be in this case those caches are not properly being invalidated. I would look there.

smithkm commented 10 years ago

Yep, that was it.