On Thu, May 26, 2011 at 9:10 AM, web <[email protected]> wrote: > Hi, > > We would like to put Geoserver into a custom cloud environment composed by a > frontal load balancer that can raise many instances depending on the load, > cpu/mem usage, the request is then dispatched to an instance. It is totally > transparent to the user, so if a request is addressed to Geoserver, you'll > never know on which instance it will go. Therefore these many instances must > share the same Geoserver config. The question remains: are we going to face > data inconsistency because many instances are editting the non-synchronized > file-based Geoserver config? This is why I thought about using the db config > plugin, to avoid these problems (even if I'm not sure it will help that > way..).
What you're looking at are the typical clustered deployment issues, cloud or not. You'll need to have all the GeoServer instancies use the same shared data directory, and also have a way to synchronize them when the configuration changes on one. > However what we mostly do with Geoserver is creating/editing featuretypes, > layers and styles. And our users have separate namespaces and do not edit > resources from other ones, only their owns. So maybe sharing the file based > config between the instances would be sufficient? This might be indeed tricky, as Geoserver caches the configuration fully in memory. Every time the configuration changes you need to force the other instances in the cluster to reload the config from files, which is possible via a rest config call. In your case you have multiple admins though, it might get tricky, the reload might indeed result in inconsistencies and errors, if files are changed during a reload the reader may find an unfinished xml file to read (as far as I remember we follow a "write and rename" approach, so that should not happen much... I'd suggest you add a restlet to do only a partial reload instead, one that only forces the reload of a single workspace. You do have a single admin per workspace, do you? Btw, how do you manage to give per workspace administration? GeoServer still does not have the notion of a "partial" administrator? The GS admin is, today, like root on Unix systems, it's all powerful. Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
