Last modified: 2006-04-17 17:21:59 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 5624 - update procedure for special pages needs more transparency
update procedure for special pages needs more transparency
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-17 17:13 UTC by Stefan Bauer
Modified: 2006-04-17 17:21 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Stefan Bauer 2006-04-17 17:13:28 UTC
Most special pages deliver only cached content, mostly updated every few days
but sometimes there is no update for quite a long time - e.g. for nearly 4 weeks
in march and now for more than a week. This fact is more than annoying for
maintenance.

Most no-update-periods are after outages when the side was down. I hope there
are reasons for not updating - but sometimes I have the feeling they are just
forgotten.

There should be more transparency for these aspects:
- First the timestamp for the last update should be added to the special pages
- Second there should be given reasons why these pages are not updated
Comment 1 Rob Church 2006-04-17 17:21:59 UTC
First, the timestamp will be present on all cached data sets as of the next
update. Second, the updates are scheduled on a regular basis; this is of course
going to be interrupted if the servers kick the bucket. The reason for the
caching is that of performance and load; some of the queries used to produce
those reports would kill our slaves if run on each view.


Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links