Bug 470855 - condor_schedd logs incorrect number of idle jobs
Summary: condor_schedd logs incorrect number of idle jobs
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: 2.2
: ---
Assignee: Timothy St. Clair
QA Contact: Kim van der Riet
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-10 16:54 UTC by Matthew Farrellee
Modified: 2012-02-14 19:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-14 19:36:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Matthew Farrellee 2008-11-10 16:54:14 UTC 
Description of problem:

The condor_schedd logs about the number of idle jobs, but does so incorrectly.


Version-Release number of selected component (if applicable):

exists since at least 7.0.5


How reproducible:

Always


Steps to Reproduce:
1. start a clean schedd
2. monitor SchedLog
3. submit 512 jobs that do not run
4. in SchedLog, watch for: Out of servers - 0 jobs matched, 512 jobs idle, 1 jobs rejected
5. rm the jobs
6. in SchedLog, watch for: Out of servers - 0 jobs matched, 512 jobs idle, 0 jobs rejected


Expected results:

I would expect the log to mention 0 jobs idle when in fact there are 0 idle jobs.


Additional info:

This appears to be related to HashTable iteration. Possibly jobs are not being purged when they are removed from the queue. The jobs are counted by walking the queue with get_job_prio in qmgmt.C.
Comment 2 Timothy St. Clair 2012-02-14 19:36:57 UTC 
log delta is not the same anymore, match line appears differently post asyn negotiation.
Note You need to log in before you can comment on or make changes to this bug.