Maniphest T101967

Recommend setting up a job runner as part of new installation
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	TheDJ
	Jun 10 2015, 10:59 AM

Description

On MediaWiki Support Desk, I'm seeing tons of small site users that are having a lot of problems since 1.24 and 1.25 with out of date content.

All this has to do with the fact that the JobRunner is doing so much more, that the default job runner rate, simply isn't really sufficient for those types of sites anymore. Just like other large sites, they really should run it continuously.

I think we should take a hint from phabricator here and advise users to setup this up during install, if the system really has become so dependent on it.

Event Timeline

TheDJ created this task.Jun 10 2015, 10:59 AM

TheDJ raised the priority of this task from to Needs Triage.

TheDJ updated the task description. (Show Details)

TheDJ added projects: WMF-JobQueue, MediaWiki-Installer.

TheDJ subscribed.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 10 2015, 10:59 AM

Some more links:

I updated the documentation page, adjusting the info about the HTML cache invalidation job, since it implied that the invalidation was done inmediately and only delayed if more than 500 needed invalidation, but that isn't true at least on recent versions. Maybe that was changed and is the cause of more reports lately.

cc'ing @aaron since he's usually involved in job queue improvements

Krinkle renamed this task from Make the Job runner a standerd (daemon) service for new installs to Recommend setting up a job runner as part of new installation.Jul 7 2017, 9:15 PM

Krinkle edited projects, added MediaWiki-Core-JobQueue; removed WMF-JobQueue.

Recommend setting up a job runner as part of new installationOpen, Needs TriagePublicActions

Description

Event Timeline

Recommend setting up a job runner as part of new installation
Open, Needs TriagePublic
Actions