[YARN-7952] RM should be able to recover log aggregation status after restart/fail-over - ASF JIRA

XML

Word

Printable

JSON

Details

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

Hadoop Flags:

Reviewed

Description

Right now, the NM would send its own log aggregation status to RM periodically to RM. And RM would aggregate the status for each application, but it will not generate the final status until a client call(from web ui or cli) trigger it. But RM never persists the log aggregation status. So, when RM restarts/fails over, the log aggregation status will become “NOT_STARTED”. This is confusing, maybe we should change it to “NOT_AVAILABLE” (will create a separate ticket for this). Anyway, we need to persist the log aggregation status for the future use.

Attachments

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

YARN-7952-poc.patch
01/Mar/18 01:11
31 kB
Xuan Gong
YARN-7952.1.patch
01/Mar/18 15:27
36 kB
Xuan Gong
YARN-7952.2.patch
05/Mar/18 05:28
42 kB
Xuan Gong
YARN-7952.3.patch
07/Mar/18 05:49
44 kB
Xuan Gong
YARN-7952.3.patch
07/Mar/18 06:20
44 kB
Xuan Gong
YARN-7952.5.patch
08/Mar/18 00:21
44 kB
Xuan Gong
YARN-7952.6.patch
08/Mar/18 10:02
45 kB
Xuan Gong
YARN-7952.7.patch
09/Mar/18 02:46
46 kB
Xuan Gong
YARN-7952.8.patch
14/Mar/18 07:33
46 kB
Xuan Gong
YARN-7952.9.patch
14/Mar/18 23:59
47 kB
Xuan Gong

Issue Links

relates to

YARN-10368 Log aggregation reset to NOT_START after RM restart.

Open

Activity

People

Assignee:: Xuan Gong

Reporter:: Xuan Gong

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 21/Feb/18 03:08

Updated:: 27/Jul/20 09:10

Resolved:: 15/Mar/18 20:51