[
https://issues.apache.org/jira/browse/YARN-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916485#comment-16916485
]
Bilwa S T edited comment on YARN-9785 at 8/27/19 7:55 AM:
----------------------------------------------------------
In LeafQueue#activateApplications there is a lessThanOrEqual to check for
amResourceRequest and amlimit for a queue which in turn calls
DominantResourceAllocator#compare as GPU resource is zero.
DominantResourceAllocator#compare returns 0 as lhsMemory > rhsMemory &&
lhsvcore < rhsVcore which would return true and then application gets
activated. To solve this lessThanOrEqual should make sure that none of the lhs
resource is greater than rhs resource
was (Author: bilwast):
In LeafQueue#activateApplications there is a lessThanOrEqual to check for
amResourceRequest and amlimit for a queue which in turn calls
DominantResourceAllocator#compare as GPU resource is zero.
DominantResourceAllocator#compare returns 0 as lhsMemory > rhsMemory &&
lhsvcore < rhsVcore which would return true and then application gets
activated.
> Application gets activated even when AM memory has reached
> ----------------------------------------------------------
>
> Key: YARN-9785
> URL: https://issues.apache.org/jira/browse/YARN-9785
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bilwa S T
> Assignee: Bilwa S T
> Priority: Blocker
>
> Configure below property in resource-types.xml
> {quote}<property>
> <name>yarn.resource-types</name>
> <value>yarn.io/gpu</value>
> </property>
> {quote}
> Submit applications even after AM limit for a queue is reached. Applications
> get activated even after limit is reached
> !queue.png!
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
