[YARN-433] When RM is catching up with node updates then it should not expire acquired containers - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Sub-task
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.8.0, 3.0.0-alpha1
Component/s: resourcemanager
Labels:
None

Hadoop Flags:

Reviewed

Description

RM expires containers that are not launched within some time of being allocated. The default is 10mins. When an RM is not keeping up with node updates then it may not be aware of new launched containers. If the expire thread fires for such containers then the RM can expire them even though they may have launched.

Attachments

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

YARN-433.1.patch
16/Jun/15 01:26
11 kB
Xuan Gong
YARN-433.2.patch
17/Jun/15 21:56
12 kB
Xuan Gong
YARN-433.3.patch
16/Jul/15 20:17
11 kB
Xuan Gong
YARN-433.4.patch
21/Jul/15 16:56
12 kB
Xuan Gong

Activity

People

Assignee:: Xuan Gong

Reporter:: Bikas Saha

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Dates

Created:: 27/Feb/13 23:05

Updated:: 30/Aug/16 01:32

Resolved:: 31/Jul/15 05:10