Warning: This page has not been updated in over over a year and may be outdated or deprecated.
administration:fault_tolerance_and_load_balancing
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
administration:fault_tolerance_and_load_balancing [2015/12/14 19:45] – demiankatz | administration:fault_tolerance_and_load_balancing [2023/03/30 00:46] – cmurdoch | ||
---|---|---|---|
Line 13: | Line 13: | ||
Below are two example configurations: | Below are two example configurations: | ||
- | {{: | + | {{: |
=== Front-End Sessions === | === Front-End Sessions === | ||
When configuring a load-balancer, | When configuring a load-balancer, | ||
There are two primary strategies for dealing with this issue: | There are two primary strategies for dealing with this issue: | ||
+ | |||
== Node Persistence == | == Node Persistence == | ||
Most load-balancers can be configured such that a user will always hit the same node during their session. This is often referred to as sticky sessions. The strategies for achieving this goal depend on the load balancer but can range from using cookies to keeping track of IP addresses. Consult the documentation for the load balancer to learn about the strategies available. | Most load-balancers can be configured such that a user will always hit the same node during their session. This is often referred to as sticky sessions. The strategies for achieving this goal depend on the load balancer but can range from using cookies to keeping track of IP addresses. Consult the documentation for the load balancer to learn about the strategies available. | ||
Line 26: | Line 27: | ||
If sessions are stored inside a local database instance on a node (MySQL/ | If sessions are stored inside a local database instance on a node (MySQL/ | ||
- | * MariaDB Galera Cluster: [[https://downloads.mariadb.org/mariadb-galera/]] | + | * MariaDB Galera Cluster: [[https:// |
==== Solr Replication ==== | ==== Solr Replication ==== | ||
There are two primary options for keeping multiple Solr nodes synchronized: | There are two primary options for keeping multiple Solr nodes synchronized: | ||
* SolrCloud: [[https:// | * SolrCloud: [[https:// | ||
- | * Traditional | + | * Traditional Replication: |
===== Example Configuration ===== | ===== Example Configuration ===== | ||
Line 109: | 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' | ||
+ | * 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 == | ||
Line 115: | Line 124: | ||
* At the time of writing this it's not recommended to run Piwik in a load balancer environment like this. A [[http:// | * At the time of writing this it's not recommended to run Piwik in a load balancer environment like this. A [[http:// | ||
---- struct data ---- | ---- struct data ---- | ||
+ | properties.Page Owner : | ||
---- | ---- | ||
administration/fault_tolerance_and_load_balancing.txt · Last modified: 2023/03/30 19:31 by cmurdoch