https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Aaron Schulz aschulz4...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #48 from Gerrit Notification Bot gerritad...@wikimedia.org ---
Related URL: https://gerrit.wikimedia.org/r/59414 (Gerrit Change
I3889f300012aeabd37e228653279ad19b296e4ae)
--
You are receiving this mail because:
You are on the CC
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #47 from Andre Klapper aklap...@wikimedia.org ---
(In reply to comment #46)
Related URL: https://gerrit.wikimedia.org/r/58415
Aaron's three-liner patch is still awaiting review.
--
You are receiving this mail because:
You are on
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #46 from Gerrit Notification Bot gerritad...@wikimedia.org ---
Related URL: https://gerrit.wikimedia.org/r/58415 (Gerrit Change
I3889f300012aeabd37e228653279ad19b296e4ae)
--
You are receiving this mail because:
You are on the CC
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Rob Lanphier ro...@wikimedia.org changed:
What|Removed |Added
Assignee|s...@reedyboy.net
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #44 from Roan Kattouw roan.katt...@gmail.com ---
(In reply to comment #43)
(In reply to comment #42)
Wait. I can not believe MediaWiki is sending pages with Cache-Control:
max-age=2592000 (2592000 = 30 days in seconds).
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #42 from Jesús Martínez Novo (Ciencia Al Poder)
martinezn...@gmail.com ---
Wait. I can not believe MediaWiki is sending pages with Cache-Control:
max-age=2592000 (2592000 = 30 days in seconds).
I've accessed that page as anon and
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #43 from Bawolff (Brian Wolff) bawolff...@gmail.com ---
(In reply to comment #42)
Wait. I can not believe MediaWiki is sending pages with Cache-Control:
max-age=2592000 (2592000 = 30 days in seconds).
I've accessed that page as
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #41 from Roan Kattouw roan.katt...@gmail.com ---
I had a chat about this with Greg, Aaron, Peter and Asher.
We realized that we have pages in our cache that were generated more than 30
days ago, most likely due to a phenomenon I'm
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #28 from Ariel T. Glenn ar...@wikimedia.org ---
(In reply to comment #27)
We have been running /usr/local/bin/mwscript purgeParserCache.php with
--age=2592000 for a couple months now (see r38275), did you not agree with
this?
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #29 from Sam Reed (reedy) s...@reedyboy.net ---
Tim suggested that it didn't seem to be working..
mysql:wikiadmin@pc1001 [parsercache] SELECT exptime FROM pc001 ORDER BY
exptime ASC limit 1;
+-+
| exptime
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #30 from MZMcBride b...@mzmcbride.com ---
(In reply to comment #28)
We have been running /usr/local/bin/mwscript purgeParserCache.php with
--age=2592000 for a couple months now (see r38275), [...]
You mean
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #31 from Ariel T. Glenn ar...@wikimedia.org ---
(In reply to comment #30)
Er yes, I do. :-)
(In reply to comment #29)
Ok, if it's broken maybe we should look at that.
--
You are receiving this mail because:
You are watching all
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #32 from Tim Starling tstarl...@wikimedia.org ---
(In reply to comment #28)
(In reply to comment #27)
We have been running /usr/local/bin/mwscript purgeParserCache.php with
--age=2592000 for a couple months now (see r38275),
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #33 from Tim Starling tstarl...@wikimedia.org ---
(In reply to comment #31)
(In reply to comment #30)
Er yes, I do. :-)
(In reply to comment #29)
Ok, if it's broken maybe we should look at that.
mysql:root@localhost
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #34 from Tim Starling tstarl...@wikimedia.org ---
Interestingly, this also means that now that the parser cache expiry time is
back to 12 months, purgeParserCache.php will purge 95% of the parser cache on
Saturday night, as fast as
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #35 from Sam Reed (reedy) s...@reedyboy.net ---
And of course, due to Timo creating all those checkouts again, we've no way of
confirming that the fix has actually fixed anything, as users getting old pages
(from 1.21 at least) will
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Bartosz Dziewoński matma@gmail.com changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #36 from Sam Reed (reedy) s...@reedyboy.net ---
(In reply to comment #35)
They're going to have to go again
Or just delete/break the symlinks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #37 from Tim Starling tstarl...@wikimedia.org ---
(In reply to comment #34)
Interestingly, this also means that now that the parser cache expiry time is
back to 12 months, purgeParserCache.php will purge 95% of the parser cache on
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #38 from Sam Reed (reedy) s...@reedyboy.net ---
Timo: Could we add some sort of JS workaround, that if a page loads and there's
missing (specific) resources, the page get's purged and maybe even refreshed?
--
You are receiving
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #39 from MZMcBride b...@mzmcbride.com ---
For reference:
(Reedy's original commit)
If7dad7f5a8b0081f1118941f4aa63e963986cf6a
(In reply to comment #27)
I reverted [...]
Ic453ad0a10a7189c0f3281c06f98227c57cbf81d
(In reply to
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #40 from Ariel T. Glenn ar...@wikimedia.org ---
(In reply to comment #33)
+-+--+
| mo | count(*) |
+-+--+
| 2013-02 | 2144 |
| 2013-03 |44279 |
| 2013-04 | 298564 |
| 2014-02 |
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #27 from Tim Starling tstarl...@wikimedia.org ---
(In reply to comment #26)
So that change is now live.
I reverted it. I thought I was pretty clear that I didn't think it was a good
idea.
--
You are receiving this mail because:
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #26 from Ariel T. Glenn ar...@wikimedia.org ---
So that change is now live. still a few things pending, recording them here so
we don't forget.
1) really the cron purge job should have taken care of that. it's fine that
the purge
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #23 from Krinkle krinklem...@gmail.com ---
https://wikitech.wikimedia.org/index.php?title=Server_admin_logdiff=56842oldid=56841
Bringing back checkouts of MediaWiki 1.21wmf5 - 1.21wmf1 on fenari for
[[bugzilla:44570|bug 44570]]
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Ariel T. Glenn ar...@wikimedia.org changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #25 from Krinkle krinklem...@gmail.com ---
(In reply to comment #16)
'wgParserCacheExpireTime' = array(
'default' = 86400 * 365,
),
Should we keep files around for a year? I don't think so..
Proposal to shorten it to
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #22 from Andre Klapper aklap...@wikimedia.org ---
For the records: Problem brought to a wider audience:
http://lists.wikimedia.org/pipermail/wikitech-l/2013-February/066770.html
--
You are receiving this mail because:
You are
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #21 from Krinkle krinklem...@gmail.com ---
(In reply to comment #20)
Maybe a solution would be to change the way we're dealing with versioning.
Instead of creating new directories for each wmfbranch, place all of them in
the same
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #20 from Jesús Martínez Novo (Ciencia Al Poder)
martinezn...@gmail.com ---
Maybe a solution would be to change the way we're dealing with versioning.
Instead of creating new directories for each wmfbranch, place all of them in
the
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Bawolff (Brian Wolff) bawolff...@gmail.com changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #13 from Sam Reed (reedy) s...@reedyboy.net ---
*** Bug 42858 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #14 from Krinkle krinklem...@gmail.com ---
We're still serving links to 1.21wmf1 and 1.21wmf2.
I propose we:
* Short term: Stop deleting branches from now on.
* Short term: Re-deploy missing versions between 1.21wmf1 and current
*
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #15 from Krinkle krinklem...@gmail.com ---
(In reply to comment #14)
We're still serving links to 1.21wmf1 and 1.21wmf2.
I propose we:
* Short term: Stop deleting branches from now on.
* Short term: Re-deploy missing versions
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #16 from Sam Reed (reedy) s...@reedyboy.net ---
'wgParserCacheExpireTime' = array(
'default' = 86400 * 365,
),
Should we keep files around for a year? I don't think so..
Considering we still have space issues on some machines
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #17 from MZMcBride b...@mzmcbride.com ---
(In reply to comment #15)
* Long term: Modify references to not be hardcoded in the main html output,
so that this doesn't matter anymore and it is all handled by ResourceLoader
instead.
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #18 from Krinkle krinklem...@gmail.com ---
(In reply to comment #17)
(In reply to comment #15)
* Long term: Modify references to not be hardcoded in the main html output,
so that this doesn't matter anymore and it is all
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Greg Grossmeier g...@wikimedia.org changed:
What|Removed |Added
CC||g...@wikimedia.org
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Andre Klapper aklap...@wikimedia.org changed:
What|Removed |Added
Summary|Time prior to removal of|Time prior to
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Sam Reed (reedy) s...@reedyboy.net changed:
What|Removed |Added
Summary|Time prior to removal of|Time prior to
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Sam Reed (reedy) s...@reedyboy.net changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Tim Starling tstarl...@wikimedia.org changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #10 from Sam Reed (reedy) s...@reedyboy.net ---
class misc::maintenance::parsercachepurging {
system_role { misc::maintenance::parsercachepurging: description = Misc
- Maintenance Server: parser cache purging }
cron {
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
MZMcBride b...@mzmcbride.com changed:
What|Removed |Added
CC||b...@mzmcbride.com
--
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #2 from Sam Reed (reedy) s...@reedyboy.net ---
Faidon noticed this earlier this week. ;) I wonder if there was already a bug
for it. I seem to recall it being much more frequent in 1.20
Noting wmf1 was out of production in October
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #3 from Sam Reed (reedy) s...@reedyboy.net ---
Faidon noticed this earlier this week. ;) I wonder if there was already a bug
for it. I seem to recall it being much more frequent in 1.20
Noting wmf1 was out of production in October
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Sam Reed (reedy) s...@reedyboy.net changed:
What|Removed |Added
CC|krinklem...@gmail.com
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Andre Klapper aklap...@wikimedia.org changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #5 from Sam Reed (reedy) s...@reedyboy.net ---
(In reply to comment #4)
Duplicate of bug 40126?
Yup. Though I think it probably makes more sense to mark 40126 as a dupe of
this one...
--
You are receiving this mail because:
You
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Sam Reed (reedy) s...@reedyboy.net changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #7 from Sam Reed (reedy) s...@reedyboy.net ---
'wgParserCacheExpireTime' = array(
'default' = 86400 * 365,
),
Down to 28 days in https://gerrit.wikimedia.org/r/47202
--
You are receiving this mail because:
You are watching
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #8 from Sam Reed (reedy) s...@reedyboy.net ---
Note, it's not deployed! (for obvious reasons)
Though, it doesn't help us with other old stale parser cache entries laying
around.
'wgSquidMaxage' = array(
'default' = 2678400, //
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
--- Comment #9 from Sam Reed (reedy) s...@reedyboy.net ---
(In reply to comment #8)
Though, it doesn't help us with other old stale parser cache entries laying
around.
maintenance/purgeParserCache.php
Using an age option of the value we
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Krinkle krinklem...@gmail.com changed:
What|Removed |Added
CC||krinklem...@gmail.com
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Krinkle krinklem...@gmail.com changed:
What|Removed |Added
Keywords||code-update-regression
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Liangent liang...@gmail.com changed:
What|Removed |Added
CC||liang...@gmail.com
--
57 matches
Mail list logo
