Closed
Bug 454023
Opened 16 years ago
Closed 15 years ago
Sentry should automatically decrease weights on mirrors that get dropped and re-added
Categories
(Webtools :: Bouncer, defect)
Webtools
Bouncer
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: justdave, Assigned: justdave)
Details
Attachments
(1 file)
3.16 KB,
patch
|
Details | Diff | Splinter Review |
One thing we noticed during the 3.0.1 Major Update push was several of our mirrors (even a couple of the really big ones - which caused some issues) would get overwhelmed with traffic and then get dropped for being unresponsive. On the next pass, since they were no longer getting traffic and were responsive again, they'd get added back in, and immediately get dropped again on the next pass. Rinse and repeat. One of the mirrors this happened to during MU had a weight of 15000 (no, I'm not kidding) which was almost a quarter of the entire pool. You can imagine every time that got pulled, the traffic went up a LOT for everyone else in the pool. One way we thought of to possibly deal with this is to have sentry automatically decrease the weight on the mirror by a percentage (perhaps 10%) every time it gets re-added after being pulled for unresponsiveness. The original starting weight should probably be recorded somewhere... perhaps append to a comment field every time it gets dropped, or maybe just add a new column for the manually-set weight, and leave that one alone.
Assignee | ||
Comment 1•16 years ago
|
||
I spent most of Wednesday (starting at around 3am when one of the primary mirrors started misbehaving and paged me) doing this by hand. :( It was a never-ending battle.
Severity: major → critical
Assignee | ||
Comment 2•15 years ago
|
||
Assignee | ||
Comment 3•15 years ago
|
||
I committed this to the production tag a while back.
Assignee: morgamic → justdave
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•