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

Jim Challenger resolved UIMA-3335.
----------------------------------

    Resolution: Fixed

> DUCC RM: Incorrectly accounting for existing shares calculating caps
> --------------------------------------------------------------------
>
>                 Key: UIMA-3335
>                 URL: https://issues.apache.org/jira/browse/UIMA-3335
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>    Affects Versions: 1.0-Ducc
>            Reporter: Jim Challenger
>            Assignee: Jim Challenger
>             Fix For: 1.0-Ducc
>
>
> When assigning a fixed share the share order of the incoming request is 
> applied to ALL existing requests while calculating caps.  If the new request 
> is larger than the existing ones, this artificially inflates the total 
> pending usage, causing the new job to be refused for exceeding caps. 
> The fix is to count qshares correctly up front, then add in the qshares for 
> the new request, instead of being fancy and trying to convert Nshares to 
> Qshares in one fell swoop.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to