Closed
Bug 583122
Opened 14 years ago
Closed 14 years ago
Hash mismatches soon after add-on updates
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
addons.mozilla.org Graveyard
Public Pages
Tracking
(Not tracked)
RESOLVED
FIXED
5.11.7
People
(Reporter: zandr, Assigned: jbalogh)
References
Details
Every time we release a new version of Weave/Sync, we get a flurry of hash mismatches when people try to download the new plugin. Bug 583036 is the latest instance of this. It will go away after a few hours, but it's a problem when we're trying to drive interest around a new release and it looks broken. We updated Sync at about 9:30 this morning, and were still seeing hash mismatches around noon. A brief conversation with jbalogh on #webdev seems to indicate that it's a problem with zamboni and remora moving at different speeds, and he has an idea how to fix it. I suspect there may be issues with caches/load balancers in front of AMO, but one thing at a time.
Assignee | ||
Comment 1•14 years ago
|
||
We're fighting against three layers of caching here: 1. zamboni gives the addons table a current_version field which is a link to the latest public/approved/experimental version. This saves us from doing complicated queries with multiple joins every time we want an add-on. 2. We store queries and Addon objects in memcached. 3. Zeus caches full HTML pages. The problem is with #1, since remora doesn't know about current_version. It's running the query we wanted to avoid and finding the real latest version. That's where we get the hash mismatch, which then gets exacerbated by the two levels of caching above. In bug 582453 we moved the cron that updates current versions from every three hours to every 20 minutes, and made sure the query it runs is not cached. http://github.com/jbalogh/zamboni/commit/17698c6 does it even better, using a lighter query that we can run every minute. Bug 583079 will let us turn on redis and enable invalidation of memcached objects. Bug 583121 will flush zeus caches when we update an add-on.
Assignee | ||
Comment 2•14 years ago
|
||
Calling this fixed, the dependent bugs are good enough for this all to work.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 4•14 years ago
|
||
I still periodically (on each public update) receive complaints like this: http://forums.informaction.com/viewtopic.php?p=22425#p22425 They usually fade out in 24 hours or so, but I wouldn't call it "fixed" anyway.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 5•14 years ago
|
||
Bug 591028 is switching the downloads backend to python, so it will match whatever the frontend is thinking.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Comment 6•14 years ago
|
||
When does it go live?
Comment 7•14 years ago
|
||
Nov 9th. See https://mail.mozilla.com/home/wclouser@mozilla.com/AMO%20Schedule.html
Updated•8 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•