Bug 476779 - Job Router doesn't recognize routed job complete
Job Router doesn't recognize routed job complete
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid (Show other bugs)
All Linux
urgent Severity urgent
: 1.1
: ---
Assigned To: Matthew Farrellee
Jeff Needle
Depends On:
  Show dependency treegraph
Reported: 2008-12-16 21:51 EST by Robert Rati
Modified: 2009-02-04 11:04 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-02-04 11:04:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Rati 2008-12-16 21:51:25 EST
Description of problem:
When a cluster of 10 jobs is submitted, the jobs all run to completion (routed jobs shutdown), but the job router never recognizes that the routed job as completed so the source jobs never complete and go through the finalization process.

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Matthew Farrellee 2008-12-18 13:02:22 EST
Fix will be present after 7.2.0-0.13

commit 915980142bb380619c6a7677f44b04f3277058b7
Author: Matthew Farrellee <matt>
Date:   Thu Dec 18 11:19:30 2008 -0600

    Fixed a dirty write bug in the JobRouter's Status Hook
    The JobRouter would get a copy of an ad from the ClassAdCollection and
    spawn the hook. While the hook was executing the JobRouter would
    update the ad the hook was working on. When the hook returned the
    stale ad would be used for updates. The result was stale data would
    overwrite current data.
    The fix is to sync the ad with the ClassAdCollection when the hook
Comment 4 errata-xmlrpc 2009-02-04 11:04:15 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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