Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+Highest\s+weight\s+only\s+scheduling\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+Highest\s+weight\s+only\s+scheduling\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [lvs-users] Highest weight only scheduling (score: 1): Author: Rob Smith <kormoc@xxxxxxxxx>; Date: Fri, 25 Jan 2013 16:09:30 -0800; Hi Anders, Thank you for the very informative and comprehensive reply. We decided that using 65535/1 would work well enough for our use case. Thanks again, ~Rob ______________________________________; /html/lvs-users/2013-01/msg00007.html (9,136 bytes)
2. Re: [lvs-users] Highest weight only scheduling (score: 1): Author: Anders Henke <anders.henke@xxxxxxxx>; Date: Thu, 24 Jan 2013 12:50:56 +0100; None of the current IPVS schedulers do know "highest weight" balancing. With the "weighted" schedulers, you can e.g. give your primary server a weight of max. 65535 and your secondary server a weight; /html/lvs-users/2013-01/msg00006.html (11,627 bytes)
3. [lvs-users] Highest weight only scheduling (score: 1): Author: Rob Smith <kormoc@xxxxxxxxx>; Date: Wed, 23 Jan 2013 14:28:54 -0800; Hi everybody, I have a keepalived setup with three servers behind an ip. One is setup as a sorry server and only serves the maintenance pages, the other two are actual servers. We would like it setup; /html/lvs-users/2013-01/msg00003.html (8,949 bytes)

Current List: 1 - 3
Page: [1]