[Spread-users] One scabby sheep will mar a whole frock
jschultz at spreadconcepts.com
Fri Feb 1 11:07:08 EST 2008
The only way I can think would be to have daemons monitor their load and
if it gets too high, then to voluntarily exclude themselves from the
membership for a significant period of time (e.g. - at least a minute).
This would require "vetoing" the current membership in which it resides by
purposely holding the token until the membership times out. Plus, the
deamon would have to ignore Spread traffic from all other daemons for the
exclusion period of time. In addition, you probably wouldn't want to
rejoin the system until the load had dropped significantly below your
exclusion loading threshold to further prevent thrashing.
Other ways of dealing with this are to give Spread real time priority or
nicing it to very high priority.
Phn: 443 838 2200
On Fri, 1 Feb 2008, Lobiv Igor wrote:
> I've red in docs "A user guide to spread Version 10.11"
> 2.4 Tuning spread for performance or unique situations
> 2.4.2 Spread in high-load environments
> End of the page 19, begin of the page 20
> "Since all the daemons in the membership rely on all the others to quickly process the token, send out new packets and then forward the token on,
> if even ONE machine is heavily loaded the token will be significantly slowed
> and ALL Spread daemons will be slowed."
> Is exist way to change this property of spread? May be automatically exclude daemons which load is increased up to X%? X is configured in config file.
> Best regards,
> Igor Lobiv
> Telco Software Development Sector
> SITRONICS Telecom Solutions, Czech Republic a.s.
> Tel.: +420 211 030 655, Mobile: +420 724 936 638, Fax: +420 296 524 103
> BB Centrum - Beta, Vyskočilova 1461/2b, 140 00 Praha 4, Czech Republic
> Spread-users mailing list
> Spread-users at lists.spread.org
More information about the Spread-users