Are we still throttling major updates for 1.5.0.x -> 2.0.0.x?

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
11 years ago
3 years ago

People

(Reporter: (not reading, please use seth@sspitzer.org instead), Assigned: aravind)

Tracking

Details

(URL)

Are we still throttling major updates for 1.5.0.x -> 2.0.0.x?

I'm getting around 50% "update to 2.0.0.4 snippets" and 50% "empty update" snippets for https://aus2.mozilla.org/update/1/Firefox/1.5.0.12/2007050813/WINNT_x86-msvc/en-US/release/update.xml

This is on 7/18/07 at 9 am PST (right after the release of 2.0.0.5)

I thought we disabled throttling?
(Assignee)

Comment 1

11 years ago
We enabled it last night because bouncer was killing the db.  We will open things up once the load settles down.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
Assignee: morgamic → aravind
Component: General → Server Operations
OS: Windows XP → All
Product: AUS → mozilla.org
QA Contact: general → justin
Hardware: PC → All
Version: 2.0 → other
Ted writes:

<justdave> fyi, aus got throttled this morning
<justdave> about an hour ago
<justdave> DB stablized with the throttle rate at 45%
<justdave> everything got buried shortly after the east coast US came
online for the business day

Verifying that we enabled throttling.  (Or should we verify when throttling is disabled?)

Comment 3

11 years ago
(In reply to comment #1)
> We enabled it last night because bouncer was killing the db.  We will open
> things up once the load settles down.

Why was bouncer killing the DB?

I'd like to understand/fix/address that issue.

Reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 4

11 years ago
Bouncer shares its db with a few other applications.

Under full capacity, all of the available database connections are being taken up by bouncer, starving the other applications.

I found no way to throttle db connections per user/db, so the only way to get other apps to work is throttle the bouncer app itself.

The fix is to either move bouncer off to its own db or to rewrite the app, so it uses connections better.

What else would you like to know?

Comment 5

11 years ago
Throttling is off now - I'll open another bug for the fix of bouncer against webapp.
Status: REOPENED → RESOLVED
Last Resolved: 11 years ago11 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.