Has anyone tried to load balance an (un-clustered) Matrix, even just as a proof of concept?
Ignoring all writing issues (so no authoring, no form submission), one load balancing server sends requests to two different boxes who share the same mounted data/ (cache/ as well?) and DB. Any idea how MySource would handle it? The aforementioned is highly simplifying load balancing issues but may help identifying some problems (or not?).
I know there is currently a lot of work being done on HA/DR.
Could we have an update on how that is progressing on the forum?
Greg answered some of the above questions in this thread: MySQL/MySource Replication
I've managed to get simple load balancing going by sharing the entire matrix installation using nfs and using a single postgres installation that all the webserver connect to. Then you use LVS on another machine to balance the requests across the machines. Wasn't too hard to setup actually.
One thing to note though is that the path to matrix on the filesystem MUST be the same on both servers otherwise you will have problems.
Also I wasn't able to get squiz server working in this sort of setup although to be honest I havn't really had a serious attempt at that since next thing I am trying is postgres replication.
Apparantly in this sort of setup the backend was alot more responsive (according to one of the developers) although personally I didn't really notice the difference.
It might have just been beacuse the servers wern't doing anything else at the time but to offset that they were pretty old machines without much ram.
In a non-clustered scenario (ie. Apache/Matrix on a node, mutliple nodes, load balancer above it), if all the nodes share the same data folder, and the load balancer takes care of the stickiness (ie. User starting to browse on a node stays on that node): would there be an issue with having different cache/ on each node?
I guess one could think of it in the following way: are the cache/ and data/ linked in any way? cache/ and DB?
Cache is used for storing session files. So if a user starts a session on one server, then moves to another, PHP wont be able to find their session information so they will be logged out.