It should no longer be required to have a shared file system, GSIP-106
<https://github.com/geoserver/geoserver/wiki/GSIP-106> removed file
references form the codebase allowing you to plug in alternate storage for
configuration (styles, icons, fonts, templates). Previously only the
catalog and settings were isolated from the file system.
Your dcos-geoserver solutions is interesting, I have seen teams use version
control on their data directory for a similar effect. As part of the work
done around the backup restore package - a chance was made allowing your to
use variable substitution data store path locations - which may be a good
fit for your cluster if they do not all have a shared disk.
Have you tried the jms-cluster or jdbc-config approaches? They take two
different approaches to notifying nodes in the cluster and can point at how
integration can be done.
--
Jody Garnett
On 11 July 2017 at 15:19, Jonathan Meyer <[email protected]> wrote:
> Greetings. I've been a long time user of GeoServer / occasional
> contributor, and I was interested in the general direction the developers
> envisioned GeoServer moving with regards to deployment scalability.
> Specifically with regard to supporting master-less horizontal scalability
> in a Apache Mesos / Kubernetes / etc. cluster environment.
>
> As background, I'm aware of various efforts / documentation on how to
> coordinate GeoServer configuration between multiple instances:
> http://docs.geoserver.org/latest/en/user/community/jms-cluster/index.html
> https://boundlessgeo.com/2013/04/geoserver-in-a-clustered-
> configuration-part-1/
> https://2016.foss4g-na.org/sites/default/files/slides/High%20Performance%
> 20Geoserver%20Clusters_0.pdf
>
> In developing a GeoServer package for Apache Mesos via DC/OS, I went down
> a similar path to Derek Kern as identified in his 2016 FOSS4G-NA talk
> (linked above) - mounted network storage to share GeoServer data
> configuration across multiple machines. While this solution is functional,
> it enforces a requirement on consistent mounted data across a cluster, as
> well as requiring an external coordination service to monitor configuration
> directory and force instances to reload from disk. My preferred approach
> would be to either directly coordinate between GeoServers or use a cluster
> native coordination system (such as Zookeeper) for configuration. I have
> considered looking into using the GeoServer backup/restore plugin that was
> recently developed to push configuration to all other GeoServer instances
> within a cluster.
>
> Does any one else have experience or opinions in this domain? I'm just
> brainstorming and would love to discuss this in more detail.
>
> Also, any feedback on the DC/OS GeoServer package would be welcomed:
> http://universe.serv.sh/#/package/geoserver/version/latest
> https://github.com/appliedis/dcos-geoserver
>
> v/r,
> Jonathan Meyer
> Sr. Software Engineer
> Applied Information Sciences
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
