[YARN-392] Make it possible to specify hard locality constraints in resource requests - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Sub-task
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 2.1.0-beta
Fix Version/s: 2.1.0-beta
Component/s: resourcemanager
Labels:
None

Hadoop Flags:

Reviewed

Description

Currently its not possible to specify scheduling requests for specific nodes and nowhere else. The RM automatically relaxes locality to rack and * and assigns non-specified machines to the app.

Attachments

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

YARN-392.patch
18/Feb/13 06:04
24 kB
Sandy Ryza
YARN-392-1.patch
29/Mar/13 00:50
5 kB
Sandy Ryza
YARN-392-2.patch
09/May/13 19:54
12 kB
Sandy Ryza
YARN-392-2.patch
18/Apr/13 20:34
12 kB
Sandy Ryza
YARN-392-2.patch
18/Apr/13 20:26
12 kB
Sandy Ryza
YARN-392-3.patch
10/May/13 23:04
18 kB
Sandy Ryza
YARN-392-4.patch
14/May/13 20:56
19 kB
Sandy Ryza
YARN-392-5.patch
20/May/13 21:42
19 kB
Sandy Ryza
YARN-392-6.patch
21/May/13 00:09
19 kB
Sandy Ryza
YARN-392-7.patch
21/May/13 21:50
20 kB
Sandy Ryza
YARN-392-8.patch
23/May/13 18:29
20 kB
Sandy Ryza

Issue Links

is depended upon by

YARN-521 Augment AM - RM client module to be able to request containers only at specific locations

Closed

is related to

YARN-393 In RM * is overloaded for locality as well as resource demand

Open

Activity

People

Assignee:: Sandy Ryza

Reporter:: Bikas Saha

Votes:: 0 Vote for this issue

Watchers:: 23 Start watching this issue

Dates

Created:: 12/Feb/13 00:15

Updated:: 27/Aug/13 22:15

Resolved:: 31/May/13 17:32