[YARN-7739] DefaultAMSProcessor should properly check customized resource types against minimum/maximum allocation - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Blocker
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.1.0, 2.10.1
Component/s: None
Labels:
None

Target Version/s:

3.1.0
Hadoop Flags:

Reviewed

Description

Currently, YARN RM reject requested resource if memory or vcores are less than 0 or greater than maximum allocation. We should run the check for customized resource types as well.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

YARN-7339.002.patch
31/Jan/18 04:34
17 kB
Wangda Tan
YARN-7739.001.patch
29/Jan/18 07:07
17 kB
Wangda Tan

Issue Links

relates to

YARN-8202 DefaultAMSProcessor should properly check units of requested custom resource types against minimum/maximum allocation

Resolved

Activity

People

Assignee:: Wangda Tan

Reporter:: Wangda Tan

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: 12/Jan/18 00:38

Updated:: 09/Dec/19 19:59

Resolved:: 12/Feb/18 03:13