[YARN-4132] Separate configs for nodemanager to resourcemanager connection timeout and retries - ASF JIRA

XML

Word

Printable

JSON

Details

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

Hadoop Flags:

Reviewed

Description

Being part of the cluster, nodemanagers should try very hard (and possibly never give up) to connect to a resourcemanager. Minimally we should have a separate config to set how aggressively a nodemanager will connect to the RM separate from what clients will do.

Attachments

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

YARN-4132.2.patch
08/Sep/15 20:47
7 kB
Chang Li
YARN-4132.3.patch
29/Oct/15 20:27
14 kB
Chang Li
YARN-4132.4.patch
30/Oct/15 21:32
14 kB
Chang Li
YARN-4132.5.patch
11/Nov/15 15:04
15 kB
Chang Li
YARN-4132.6.2.patch
12/Nov/15 20:00
11 kB
Chang Li
YARN-4132.6.patch
12/Nov/15 17:46
11 kB
Chang Li
YARN-4132.7.patch
20/Nov/15 22:23
12 kB
Chang Li
YARN-4132.patch
08/Sep/15 19:25
7 kB
Chang Li

Issue Links

breaks

YARN-5834 TestNodeStatusUpdater.testNMRMConnectionConf compares nodemanager wait time to the incorrect value

Resolved

relates to

YARN-4274 NodeStatusUpdaterImpl should register to RM again after a non-fatal exception happen before

Open

Activity

People

Assignee:: Chang Li

Reporter:: Chang Li

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: 08/Sep/15 19:24

Updated:: 25/Oct/19 20:25

Resolved:: 24/Nov/15 22:38