Hi, I’m having trouble with a GeoServer cluster in which we intend to use GeoFence. For configuration updates (new layers, workspaces, general configuration, etc.), initializing a reload via the GUI or via the REST-api works perfectly, but not for GeoFence. A reload has no impact at all. I assume that the reload does not work because of H2 DB locking. The only way to get a configuration change from one instance to the next is shutting down the instance where the changes were made (to release the DB lock) and restarting the instance where you want the changes to be taken over to or to apply the changes to multiple instances, but this would mean that the configuration could be out of sync unless we write sync scripts. However, I also noticed that after restarting instances something strange things happen when new rules were written to multiple instances before.
In our case the cluster uses a shared configuration folder (NFS-share mounted into the instances). We use the kartoza/geoserver docker image. Does anyone have experience with using GeoFence in a cluster? I tried to implement JMS based clustering but I was not successful in getting this stable in our case. Would this solve keeping the GeoFence configuration in sync? Kind regards, Olav
_______________________________________________ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
