X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fload_balance.xml;h=f71a29433a7cebb8d55fddf314a64f46cef38bff;hb=b0c61b7f8b17d876c88347a96c246c47493140da;hp=fb5b25ab304723fc6343313c5646f53e7d697218;hpb=ef98468ea4c580b5d3bcdae2b3889703af4fb778;p=metaproxy-moved-to-github.git diff --git a/doc/load_balance.xml b/doc/load_balance.xml index fb5b25a..f71a294 100644 --- a/doc/load_balance.xml +++ b/doc/load_balance.xml @@ -1,9 +1,10 @@ + + %idcommon; ]> - - + load_balance 3mp @@ -12,7 +13,8 @@ load_balance - balances load among Z39.50 targets + Metaproxy Module balancing load among multiple identical + Z39.50 targets DESCRIPTION @@ -20,23 +22,35 @@ This filter balances load among Z39.50 targets based on statistics gathered on number of open sessions and number of open package requests. + + The load balancing is depending on targets to be specified (vhosts). + Most Z39.50 clients do not specify that. For this reason, this + filter is mostly used as a follower to filter virt_db. + EXAMPLES - A typical configuration looks like this: + This configuration offers one database, Default, + which is load-balanced between two backend servers. + Default + host1:210/Default + host2:210/Default + ]]> + SEE ALSO - metaproxy - 1 + virt_db + 3mp