Uploaded image for project: 'Slider'
  1. Slider
  2. SLIDER-1025

Outstanding container request is not removed from open list even it is already been allocated

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: Slider 0.80, Slider 0.81
    • Fix Version/s: Slider 0.90.2
    • Component/s: core
    • Labels:
      None

      Description

      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.

      public synchronized boolean resourceRequirementsMatch(Resource resource) {
          return issuedRequest != null && issuedRequest.getCapability().equals(resource);
        }
      

      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.

        Attachments

        1. SLIDER-1025.001.patch
          1 kB
          Weiwei Yang

          Activity

            People

            • Assignee:
              cheersyang Weiwei Yang
              Reporter:
              cheersyang Weiwei Yang
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: