[
https://issues.apache.org/jira/browse/SLIDER-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved SLIDER-955.
-----------------------------------
Resolution: Fixed
Assignee: Steve Loughran
Fix Version/s: Slider 0.90.2
AppState is now building up the resource requirements from the min/max values
and normalizing, which should be what you need. Closing this -if you are still
seeing the problem re-open it.
> fail to track the outstandingRequest when submit an application that
> yarn.memory is not a multiple of minimum-allocation-mb
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: SLIDER-955
> URL: https://issues.apache.org/jira/browse/SLIDER-955
> Project: Slider
> Issue Type: Improvement
> Components: appmaster
> Affects Versions: Slider 0.80
> Reporter: kyungwan nam
> Assignee: Steve Loughran
> Fix For: Slider 0.90.2
>
>
> "yarn.scheduler.minimum-allocation-mb” is set to 256 in my cluster.
> I submit an application that “yarn.memory” is set to 7169 (not a multiple of
> 256)
> the resource of allocated container will be 7424(256*29) memory because the
> resource requirement is normalized to a multiple of
> "yarn.scheduler.minimum-allocation-mb” by RM.
> the resource requirement of outstandingRequest that is tracked by Slider AM
> does not match the resource of the allocated container.
> therefore, Slider AM can’t clean up the outstandingRequest and requests in
> AMRMClient.
> I think it should fix as following 1 or 2
> 1. an application should be able to submit only if “yarn.memory” is a
> multiple of "yarn.scheduler.minimum-allocation-mb”
> 2. the resource requirement of outstandingRequest is normalized to a multiple
> of "yarn.scheduler.minimum-allocation-mb”
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
