New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 696781 link

Starred by 1 user
Status: WontFix
Owner:
█ dshi@chromium.org
Last visit > 30 days ago
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

collect_host_stats cron job blows up virtual memory, runs over time

Reported by jrbarnette@chromium.org, Feb 27 2017 
Checking the status in top, you can see processes like this
consuming 10's of Gb of memory:
    python /usr/local/autotest/site_utils/collect_host_stats.py --span 1

Virtual memory sizes up to 48G can be seen in the process.

Moreover, you frequently find two of them.  The process represents an
hourly cron job, so to have two of them running suggests that the cron
job is now exceeding the 1 hour run window.

Comment 1 by jrbarnette@chromium.org, Feb 27 2017 

> Moreover, you frequently find two of them.  The process represents an
> hourly cron job, so to have two of them running suggests that the cron
> job is now exceeding the 1 hour run window.


More to the point, the 'ps' output clearly shows that the jobs
are overrunning the time:

UID        PID  PPID  C STIME TTY          TIME CMD
root     10099 10098  0 15:17 ?        00:00:00 /bin/sh /etc/cron.hourly/collect_host_stats_hourly
root     14544 14543  0 14:17 ?        00:00:00 /bin/sh /etc/cron.hourly/collect_host_stats_hourly

Two jobs, started exactly one hour apart...

Comment 2 by aut...@google.com, Mar 1 2017

Owner: dshi@chromium.org
dshi - who can address this?

Comment 3 by dshi@chromium.org, Mar 1 2017 

I'm handling this. I did some cleanup on the metadb, and will troubleshoot the performance issue.

Comment 4 by akes...@chromium.org, Jul 17 2017

Labels: akeshet-pending-downgrade
ChromeOS Infra P1 Bugscrub.

P1 Bugs in this component should be important enough to get weekly status updates.

Is this already fixed?  -> Fixed
Is this no longer relevant? -> Archived or WontFix
Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority.
Is this a Feature Request rather than a bug? Type -> Feature
Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign.
Does this bug have the wrong owner? -> reassign.

Bugs that remain in this state next week will be downgraded to P2.

Comment 5 by akes...@chromium.org, Jul 24 2017

Labels: -akeshet-pending-downgrade Pri-2
ChromeOS Infra P1 Bugscrub.

Issue untouched in a week after previous message. Downgrading to P2.

Comment 6 by dshi@chromium.org, Nov 20 2017

Status: WontFix (was: Available)
metadb is obsoleted.
►

Sign in to add a comment