You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Weiwei Yang (JIRA)" <ji...@apache.org> on 2015/12/15 05:49:46 UTC

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

Weiwei Yang created SLIDER-1025:
-----------------------------------

             Summary: 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.81, Slider 0.80
            Reporter: Weiwei Yang


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)