According to the documentation for flexible load balancing available here you need to:
designate a single server to be the back-office server for which your
editors will log into for editing content. Umbraco will not work
correctly if the back-office is behind the load balancer.
The fact that you can only use ONE server goes against the whole principle of load balancing.
Why is this recommended? Is it because the back-office application uses server side session? What if you use a load balancing solution that includes an affinity strategy, meaning that you always get assigned to the same server on the cluster after the first request and for as long as you keep your browser window open.
No, you must ensure that all users who access Umbraco are directed to the same server at any given time.
Otherwise, data corruption might occur, one user could edit something on server 1 whilst another user has deleted it on server 2, the cache instructions could be in the wrong order then bad things will happen especially if there are children that are now published with parents that have been deleted.
Many load balancers will allow a specific domain to be always sent to a single server, this is the ideal solution, you have www.mydomain.com that can go to any server then you have admin.mydomain.com that always goes to the same server, you access Umbraco from that one only.
So the only danger is for users to be working on the same documents and affect each other. Got it.
I'll try to configure the load balancer to send the back-office users to the same server, but if such server is down, then a new back-office server can be selected.
Load balancing and designated single back-office server
According to the documentation for flexible load balancing available here you need to:
The fact that you can only use ONE server goes against the whole principle of load balancing.
Why is this recommended? Is it because the back-office application uses server side session? What if you use a load balancing solution that includes an affinity strategy, meaning that you always get assigned to the same server on the cluster after the first request and for as long as you keep your browser window open.
Hi Javier,
No, you must ensure that all users who access Umbraco are directed to the same server at any given time.
Otherwise, data corruption might occur, one user could edit something on server 1 whilst another user has deleted it on server 2, the cache instructions could be in the wrong order then bad things will happen especially if there are children that are now published with parents that have been deleted.
Many load balancers will allow a specific domain to be always sent to a single server, this is the ideal solution, you have www.mydomain.com that can go to any server then you have admin.mydomain.com that always goes to the same server, you access Umbraco from that one only.
Jeavon
So the only danger is for users to be working on the same documents and affect each other. Got it.
I'll try to configure the load balancer to send the back-office users to the same server, but if such server is down, then a new back-office server can be selected.
Thanks.
Same documents or documents in a relationship, e.g. parent and child.
If you can configure your load balancer in that way then it will be perfect!
is working on a reply...