X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fload_balance.xml;h=5543c962b41c08bddad533d1cffca3f41bd851ab;hb=4dff8f6712101094219dd9f4bb97486416d77f9d;hp=fb5b25ab304723fc6343313c5646f53e7d697218;hpb=ef98468ea4c580b5d3bcdae2b3889703af4fb778;p=metaproxy-moved-to-github.git diff --git a/doc/load_balance.xml b/doc/load_balance.xml index fb5b25a..5543c96 100644 --- a/doc/load_balance.xml +++ b/doc/load_balance.xml @@ -1,60 +1,79 @@ - + + %idcommon; ]> - - + + + Metaproxy + Index Data + + load_balance 3mp - Metaproxy Module - - + Metaproxy Module + + load_balance - balances load among Z39.50 targets + Metaproxy Module balancing load among multiple identical + Z39.50 targets - + DESCRIPTION This filter balances load among Z39.50 targets based on statistics - gathered on number of open sessions and number of open package requests. + 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. + + + + SCHEMA + + - + 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 - + ©right;