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

["Weiwei Yang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLIDER-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057371#comment-15057371 ] 

Weiwei Yang edited comment on SLIDER-1025 at 12/15/15 5:29 AM:
---------------------------------------------------------------

We deployed a long running service via slider 0.8.0, and because of this issue, the outstanding requests never get cleaned up properly. This application takes more resources from the cluster than it actually needed, occupying unnecessary resources. Raise up the priority to Critical. Please help to review the patch and lets fix it as soon as possible. 

Thanks 


was (Author: cheersyang):
We deployed a long running service via slider 0.8.0, and because of this issue, the outstanding requests never get cleaned up properly. This application takes more resources from the cluster than it actually needed, occupying unnecessary resources. Raise up the priority to Blocker. Please help to review the patch and lets fix it as soon as possible. 

Thanks 

> 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
>            Priority: Critical
>         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)