[jira] [Resolved] (SLIDER-1025) Outstanding container request is not removed from open list even it is already been allocated

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

Steve Loughran resolved SLIDER-1025.
------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: Slider 0.91)
                   Slider 0.90

patch applied! thanks for finding and fixing this -it'll be in the 0.90-incubating release

> Outstanding container request is not removed from open list even it is already been allocated
> ---------------------------------------------------------------------------------------------
>
>                 Key: SLIDER-1025
>                 URL: https://issues.apache.org/jira/browse/SLIDER-1025
>             Project: Slider
>          Issue Type: Bug
>          Components: core
>    Affects Versions: Slider 0.80, Slider 0.81
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>            Priority: Critical
>             Fix For: Slider 0.90
>
>         Attachments: SLIDER-1025.001.patch
>
>
> When there is one or more entries in open requests list, and a container is allocated for an outstanding request, it cannot be removed from openRequests list when the resource allocated is *not matched* with the resource requested.  
> {code:java}
> public synchronized boolean resourceRequirementsMatch(Resource resource) {
>     return issuedRequest != null && issuedRequest.getCapability().equals(resource);
>   }
> {code}
> The problem here is RM doesn't always allocate *matched* resource for a request, it normalized the resource request with multiply of minimal allocation size, so instead of *matched*, it could also be *fits* the resource request.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)