Cluster configuration not resilient
Hi
We are currently running a three server cluster for performance and availability
The performance bit is fine, the three servers all share the load correctly.
We find however that if any server is shut down then the cluster goes off line.
If all three servers are restarted then the cluster has all sorts of issues and we have had to rebuild Core on a couple of occasions.
Anyone experienced this or something like it?
0
-
YES!! We had our test Geocortex Essentials instance clustered with production and analytics. Not a good idea. We declustered with the latest upgrade of analytics, so now each instance of Geocortex Core sits in it's own cluster. Support helped us with the upgrade and declustering. I would recommend talking directly with them for advice. Aaron from Latitude has been so helpful. 0 -
Thanks for your rapid reply Lara
Did you have multiple servers running Essentials with shared configration?
How do you keep the config in sync?
Thanks again0 -
That's why we had so many issues. The config for our test system was different than that for production. We maintain the config for each seperately. I currently make a change to test and then apply manually to production. But some changes we apply to test to try them and then they don't get applied to production for one reason or another. We have 2 servers running instances of Geocortex Essentials and one with Analytics. 0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
3 kommentarer