About Features Downloads Getting Started Documentation Events Support GitHub

Site Tools


administration:fault_tolerance_and_load_balancing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
administration:fault_tolerance_and_load_balancing [2017/04/11 06:27]
emaijala [Load-Balancing]
administration:fault_tolerance_and_load_balancing [2017/04/11 06:35] (current)
emaijala [Required Software Components]
Line 110: Line 110:
   ​   ​
 Now the ETag of a file will be identical on all servers as long as the modification time and file size are identical. Now the ETag of a file will be identical on all servers as long as the modification time and file size are identical.
 +
 +== Asset Pipeline and other shared files ==
 +
 +Load balancing and VuFind'​s asset pipeline are currently not compatible. The problem is that the request for which the assets were created could be served by a different server than the one the client requests them from. Without software modifications there are at least the following possibilities:​
 +  * Use a shared disk for all the load-balanced servers. This might have performance and reliability implications.
 +  * Use sticky session in the load balancer. This has its own downsides like causing future requests from clients to go to the same server as before, which could cause imbalance between the servers especially when new ones are added.
 +
 +Note that the above issues also affect things like the cover cache, but since covers can always be recreated from the source, it does not cause actual issues with servicing the requests.
  
 == Additional Implementation Notes == == Additional Implementation Notes ==
administration/fault_tolerance_and_load_balancing.txt · Last modified: 2017/04/11 06:35 by emaijala