|Resolved||None||T28439 Deploy updated WMF branch to production (February 2011)|
|Resolved||None||T29339 Bugs that should be fixed post 1.17 WMF deployment (tracking)|
|Resolved||None||T29931 Talkpage notice mails out of sync|
|Resolved||None||T29726 Rename user did not complete successfully on ar.wp|
|Resolved||None||T29798 Repeated messages about Talk page changes which have already been checked.|
|Resolved||None||T29953 Job queue is taking forever to update categorization after a template changes the category|
|Resolved||tstarling||T29727 Fix and restart job runners for Wikimedia wikis|
The job queue on English Wikipedia has been down for well over a week now and there are over 400,000 jobs stacked up waiting. See http://en.wikipedia.org/wiki/Help_talk:Job_queue#Where.27s_it_gone.3F
If this is not the correct place please advise exactly where we should be filing the bug report.
They're running, but enwiki being the biggest, will be the last to be dealt with.
So the job runners don't get stuck and stay only on the bigger wikis for a long time, they rank the smaller wikis higher...
It would seem, with like 12k being added to it in a 4 or 5 hour period, there are still big long running tasks going on. Most likely a rename.
A quick look shows that the first enwiki entry is currently a rename...
I'm asking to find out if the job runners are still running fine. Will report back
This sounds like a recipe for resource starvation. Surely taking age into account is part (I would say it should be all) of the mix?
Bear in mind that from a utilitarian POV a job entry in a big wiki queue is affecting more pages for more people...
If an even simpler sheduler were wanted - count the number of entries in a queue and do n% of them before moving to the next queue. This would get through the backlog at t0 at more or less the same time for each wiki.
Do you have a time frame on when the job queue on English Wikipedia will be dealt with? As of March 6, it's getting worse, not better.