[YARN-3488] AM get timeline service info from RM rather than Application specific configuration.

• Type: Sub-task
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Component/s: applications
• Assignee: Abhishek Modi
• Reporter: Junping Du
• Created: 15/Apr/15 01:19
• Updated: 25/Oct/19 20:26

Description

Since v1 timeline service, we have MR configuration to enable/disable putting history event to timeline service. For today's v2 timeline service ongoing effort, currently we have different methods/structures between v1 and v2 for consuming TimelineClient, so application have to be aware of which version timeline service get used there.
There are basically two options here:
First option is as current way in DistributedShell or MR to let application has specific configuration to point out that if enabling ATS and which version could be, like: MRJobConfig.MAPREDUCE_JOB_EMIT_TIMELINE_DATA, etc.
The other option is to let application to figure out timeline related info from YARN/RM, it can be done through registerApplicationMaster() in ApplicationMasterProtocol with return value for service "off", "v1_on", or "v2_on".
We prefer the latter option because application owner doesn't have to aware RM/YARN infrastructure details. Please note that we should keep compatible (consistent behavior with the same setting) with released configurations.

Issue Links

• is related to: MAPREDUCE-6327 [Event producers] Implement MapReduce AM writing MR events/counters to v2 ATS
• is required by: MAPREDUCE-7181 MR AM should get timeline service version information from RM.