Bug 695970 - Matrix report can OOMKILL Server
Summary: Matrix report can OOMKILL Server
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent vote
Target Milestone: ---
Assignee: Raymond Mancy
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-13 00:43 UTC by Bill Peck
Modified: 2019-05-22 13:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-29 07:14:51 UTC


Attachments (Terms of Use)

Description Bill Peck 2011-04-13 00:43:50 UTC
Description of problem:

The beaker matrix report doesn't have any limits on the number of jobs it will process.

Since you can select "" for whiteboard and most jobs submitted don't include a whiteboard this results in 2,285 jobs being selected.  Here are the details from David's analysis.

thread 3: frame 6 has "msg", which is 450MB of textual HTML response
data allocated on the heap being sent back through httpd output filters,
with <title>Job Matrix Report</title>

Specifically, 451515113 bytes (with commas, that's 451,515,113)

I've extracted the first and last megabyte of the message:

[root@ibm-x3950m2-02 ~]# ll *.html
-rw-r--r-- 1 root root 1048576 Apr 12 16:49 first-meg-of-msg.html
-rw-r--r-- 1 root root 1048576 Apr 12 19:25 last-meg-of-msg.html

Comment 1 Bill Peck 2011-04-13 00:44:18 UTC
Suggest we limit the number of jobs to 20 max.


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