oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OODT-439) Jobs Are Dropped When Queue Size Is Full
Date Fri, 14 Dec 2012 00:34:14 GMT

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

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

    Fix Version/s:     (was: 0.5)
                   0.6

- push out to 0.6
                
> Jobs Are Dropped When Queue Size Is Full
> ----------------------------------------
>
>                 Key: OODT-439
>                 URL: https://issues.apache.org/jira/browse/OODT-439
>             Project: OODT
>          Issue Type: Bug
>          Components: resource manager
>    Affects Versions: 0.3, 0.4
>            Reporter: Michael Cayanan
>            Priority: Minor
>             Fix For: 0.6
>
>
> When the queue has reached the max queue size, a message is logged by the Scheduler saying
there is a Job Queue Exception adding a job to the queue, and then the job is dropped.
> The following case will produce the issue:
> 1) queue is full
> 2) scheduler pops job from queue and begins trying to find a node for job
> 3) queue now has 1 open slot
> 4) another job is given to the resource manager and is placed in the queue
> 5) queue is now full again
> 6) scheduler fails to schedule popped job
> 7) scheduler pushes job back into the queue
> 8) queue is full so exception is thrown and job is lost
> The job needs to get re-queued in this case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message