Hi all,
a month ago this PR that fixes an issue with filter parameters handling in
GWC file blob storage:
https://github.com/GeoWebCache/geowebcache/pull/1230

Some context:

   - Filter parameters in GWC allow the creation of parallel caches for
   different parameter values (e.g., time, elevation, viewparam, env, anything
   hanging an effect on the tile contents)
   - Given the parameter contents might be long, complex, and not file
   system friendly, all blob storages turn them into a summary string, a SHA1,
   that identifies them (not entirely collision free, but the chance is really
   low)
   - The mapping between the sha1 and the actual set of parameter values is
   stored too. And here is where the difference is, the cloud storages store
   it in the same "folder" where the tiles are put, the file system in a
   single, centralized property file for the layer

The latter is handy, but at the same time, it creates a point of contention
among many threads/processes, and the file can grow very large (think of
long time series), exacerbating the problem to the point that even just
adding a new entry is slow. Add to that a NFS mount, and you have all the
elements for a horror movie.

The PR simply aligns the file system blobstore practice with the cloud
storage case, where the file has only one entry, is immutable past
creation, and if two processes manage to step on each other toas, they
would still produce the same file content.

And oh, the code is setup so that there is transparent migration of the
entries from the old to the new storage, so nothing is lost.

Soo... objections to backport to stable/maintenance?

Regards,

Andrea Aime


==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to