We are having some issues with our load balancing environment, where our two EPiServers (v. 10.10.0.0) doesn't always seem to agree on what to display.
/EPiServer can be accessed on both servers, and it is therefore random on which server our content editors make their changes. For 99.99% of the changes this goes well. I am assuming that the provider-based event management system in EPiServer makes sure the two servers keep each other informed about the "truth".
Sometimes however, we have problems such as:
Stuff like this happens every other day, and we have been upable to fix it.
Also, it is extremely hard to debug. We would like to take steps to force all access to /EPiServer to only take place on server 1, but our DevOps reports that in our network setup, this is not as easy as it sounds. Also, we are not sure it would solve anything.
Is there steps we can take to make sure our servers are always in sync?
Can we force a sync in another way that recycling the server that seems to disagree with the truth?
Any feedback would be greatly appreciated.Kind regardsDennis
Have you tried using the DeveloperTools, it contains some tools for remote events so you can check if there is any miscofnfiguration. I haven't used a setup with a loadbalancer in a long time, but misconfiguration was usually the problem with issues like this. There's also a NuGet package.
Thank you @Jeroen, I will take a look at the tool.
This could very well be misconfiguration, but since it is working 99.99% of the times we make changes, I don't think we completely missed something in the configuration. The servers are communicationg, just once in a while it doesn't seem to work.
Have you checked the clock on all servers is synced?
I used to have a simple "secret" page deployed on all servers that provides the facility to clear cache on that server. So if a server is not showing the up-to-date content, i browse the page using ip address and clear the cache. This however will effect performance and should only be used in rare cases like this :-)
btw, please mention which version of episerver you are on?
@Thair, that is not a bad idea, and it might be something we might have to resort too. It is slightly more efficient than recycling the webserver.
And of course - we are on version 10.10.0.0. We have had the problem for a while now, and have been keeping up with upgrades on a monthly basis.
Can anyone provide some more information about the reliability of using the default UDP Multicast for load balancing? What are the benefits over the TPC approach?
It seems that you need to look at DRBD, glusterfs, and similar products for real-time replication of your files.192.168.1.1