[
https://issues.apache.org/jira/browse/OODT-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-227.
------------------------------------
Resolution: Won't Fix
seems important, but I wonder if we can adjust with wait times and so forth.
> 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.11
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
