Hey Andrea,
Thanks so much for the info! I really appreciate your prospective. I'm
still struggling to get JMS setup in AWS. I had thought of using AmazonMQ
(hosted ActiveMQ) service as the broker service. My thought is that I
would just be able to update the brokerURL with that of the
Thanks so much for the information! I've built the JMS clustering locally
but, i've run into issues getting it to work in AWS.
Our current config is using a shared file system and JDBC - so when a
configuration change occurs, we've used the REST endpoint to reload config
across all our
Hi Jason,
As a side note, I found the JMS cluster module pretty easy to set up on a
scalable cluster deployment using docker and docker-compose.
Check out this docker-compose file [1]
It sets up a proxy and a scalable geoserver image. You should be able to do
docker-compose up -d
docker-compose
Hello Jason,
The event clustering option is in my opinion much better, I'm not sure
why "reload" is the default. The event option is indeed much smarter, it
will distribute catalog events across the different nodes, so that every
node can update its cache just for the item that changed only,
Hey Andrea,
Thanks for the reply! I appreciate your input!
Sure enough - that was the module (hz-cluster-plugin). I've installed it
and it works great, alongside JDBC and also using AWS EFS for the Geoserver
data directory. I think I agree with your assessment, it's not really
clustering as
Hi Jason,
I believe the Hazelcast clustering module alone does not really clusters
anything, it just helps
to keep the cluster up to date when you are using jdbcconfig.
The community modules are not part of releases (as they lack a maintainer),
if they are built at all you can
find them among the
Hello - I've been looking into clustering and would like to follow the
Hazelcast approach instead of the JMS. However, I'm striking out finding
the installation. I don't see it in the community modules.
Any guidance on finding the download for it?
Thanks,
Jason
