You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org> on 2012/04/01 00:30:46 UTC

[jira] [Updated] (OODT-227) Resource LRUScheduler sometimes drops jobs when 'next job' can't be scheduled

     [ https://issues.apache.org/jira/browse/OODT-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated OODT-227:
-----------------------------------

    Fix Version/s:     (was: 0.4)
                   0.5

- push to 0.5
                
> Resource LRUScheduler sometimes drops jobs when 'next job' can't be scheduled
> -----------------------------------------------------------------------------
>
>                 Key: OODT-227
>                 URL: https://issues.apache.org/jira/browse/OODT-227
>             Project: OODT
>          Issue Type: Bug
>          Components: resource manager
>         Environment: From JPL internal JIRA
>            Reporter: Brian Foster
>            Assignee: Chris A. Mattmann
>             Fix For: 0.5
>
>
> LRUScheduler pops next job off JobQueue then tries to schedule it, however if it fails to schedule that job, it tries to put the job back on the JobQueue. If the job queue was full when that next job was popped, and a remote client submits a job before LRUScheduler repushes the failed to schedule popped job, that popped job fails to added (since job queue is now full) and exception caught and ignored and job is lost.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira