All users were logged out of Bugzilla on October 13th, 2018

Why does product-details take so long to propagate?

RESOLVED FIXED

Status

RESOLVED FIXED
9 years ago
4 years ago

People

(Reporter: abuchanan, Assigned: oremj)

Tracking

Details

(URL)

(Reporter)

Description

9 years ago
The past few times I've checked in changes to product-details, I've had to wait unbearably long to see the changes propagate to stage or production.

e.g. today I waited an hour to see r66056 on www-trunk.stage

This slows down product releases and is just plain annoying.  We need to figure out why it's so slow, and make it as fast as possible.

Updated

9 years ago
Assignee: server-ops → jeremy.orem+bugs

Comment 1

9 years ago
Is this still an issue or was it a load balancer caching issue?
(Reporter)

Comment 2

9 years ago
It seemed to update much quicker today, ~15-20 minutes.

I'm always checking with ?no-cache-junk appended, so I don't suspect caching, unless there is another LB issue at play, or maybe stuck webhead updates?
(Reporter)

Comment 3

9 years ago
Checked in a p-d change ~40 minutes ago in r66309, and this page is still broken:
https://www-trunk.stage.mozilla.com/en-US/m/beta?awefawef

How does www-trunk.stage update?  Is it svn up on a cron job?  Is it kublad.py maybe?  

Possibly a cron job running svn up directly on p-d every 5 minutes would fix the problem.
(Assignee)

Comment 4

9 years ago
In this case I think one of the servers git lock needed clearing.  Should be fixed now.
Status: NEW → RESOLVED
Last Resolved: 9 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.