Junping Du created YARN-3488: -------------------------------- Summary: AM get timeline service info from RM rather than Application specific configuration. Key: YARN-3488 URL: https://issues.apache.org/jira/browse/YARN-3488 Project: Hadoop YARN Issue Type: Sub-task Components: applications Reporter: Junping Du Assignee: Junping Du
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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)