[YARN-4866] FairScheduler: AMs can consume all vcores leading to a livelock when using FAIR policy - ASF JIRA

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 2.8.0
Fix Version/s: 2.9.0, 3.0.0-alpha1
Component/s: fairscheduler
Labels:
None

Target Version/s:

2.9.0
Hadoop Flags:

Reviewed

Description

The maxAMShare uses the queue's policy for enforcing limits. When using FAIR policy, this considers only memory. If there are fewer vcores on the cluster, the AMs can end up taking all the vcores leading to a livelock.

Attachments

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

Attachments

YARN-4866.001.patch
10/May/16 21:13
5 kB
Yufei Gu
YARN-4866.002.patch
11/May/16 00:55
5 kB
Yufei Gu
YARN-4866.003.patch
11/May/16 17:37
6 kB
Yufei Gu
YARN-4866.004.patch
12/May/16 17:58
6 kB
Yufei Gu
YARN-4866.005.patch
18/May/16 20:56
6 kB
Yufei Gu
YARN-4866.006.patch
19/May/16 23:51
7 kB
Yufei Gu
YARN-4866.007.patch
25/May/16 00:23
7 kB
Yufei Gu
YARN-4866.008.patch
25/May/16 16:56
8 kB
Yufei Gu
YARN-4866.009.patch
25/May/16 18:31
9 kB
Yufei Gu

Issue Links

duplicates

YARN-3621 FairScheduler doesn't count AM vcores towards max-share

Resolved

Activity

People

Assignee:

Yufei Gu

Reporter:

Karthik Kambatla

Votes:

0 Vote for this issue

Watchers:

6 Start watching this issue

Dates

Created:

24/Mar/16 22:24

Updated:

30/Aug/16 01:04

Resolved:

26/May/16 06:26