https://bugzilla.wikimedia.org/show_bug.cgi?id=20554
--- Comment #9 from Andrew Garrett <[email protected]> 2009-11-17 22:55:15 UTC --- (In reply to comment #8) > I guess it kinda depends on how this is used, and the nature of the client. > Bots performing maintenance tasks can afford to wait for maxlag to drop, but > tools like AWB that aim to provide relatively fast user interaction don't want > to wait all day. In a scenario where one slave is badly lagged but the rest is > not, avglag could help for these slightly higher priority edits. Of course it > would need to be set to a low value like 2. Well, if your approach is "keep writing regardless of whether you lag a slave out until it's depooled", then you might as well not bother checking for slave lag at all. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
