OCG servers fill up their tmpfs
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Joe
	Oct 4 2014, 9:15 PM

Description

The tmpfs gets full because of a single page generated.

The latest offender, according to the authors.db file, is

please find out what happens as this is blocking production and requiring regular ops intervention.

Version: unspecified
Severity: blocker

• bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:45 AM

• bzimport set Reference to bz71647.

I should have added that it fills up because a 32 gb pdf file gets generated.

This happened again, for the same article, this morning. See the Server Admin Log for the timing.

I strongly suspect this has to do with the ocg service trying to embed

in the bundle/images/ dir I find one pdf file which is huge - it's a collection of scans in pdf form, which are ~ 188 MB each (per page).

As a stopgap solution, I added a <span class="noprint"> around the reference to the file, hoping this will stop the issues.

Change 165041 had a related patch set uploaded by Cscott:
Limit bundle sizes to 512MB (which should be very generous).

Change 165034 had a related patch set uploaded by Cscott:
Add options to limit bundle and image size.

Change 165041 merged by Cscott:
Limit bundle sizes to 512MB (which should be very generous).

Change 165034 merged by jenkins-bot:
Add options to limit bundle and image size.

Can't test quite yet since a crashed entry for [[Information and communication technologies for development]] is still in the status queue.