[ https://issues.apache.org/jira/browse/MAPREDUCE-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith Sharma K S updated MAPREDUCE-7062: ----------------------------------------- Summary: Update mapreduce.job.tags description for making use for ATSv2 purpose. (was: MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow versions) > Update mapreduce.job.tags description for making use for ATSv2 purpose. > ----------------------------------------------------------------------- > > Key: MAPREDUCE-7062 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7062 > Project: Hadoop Map/Reduce > Issue Type: Bug > Reporter: Charan Hebri > Assignee: Charan Hebri > Priority: Major > Attachments: MAPREDUCE-7062.001.patch > > > When applications are submitted to YARN, tags are generated in the format > > TIMELINE_FLOW_NAME_TAG:\{flow_name},TIMELINE_FLOW_VERSION_TAG:\{flow_version},TIMELINE_FLOW_RUN_ID_TAG:\{flow_run_id} > However, MR applications don't follow this format and the tags submitted via > the property mapreduce.job.tags are of the format, > {flow_name} ,\{flow_version},\{flow_run_id} > Due to this, YARN falls back to default values for flow name, flow version > and flow run id which in turn are used in ATSv2. > There are 2 approaches that could be taken to make MR tags compatible with > ATSv2, > Fix in the MR code > ------------------------- > Prefix any tags specified with the ones needed by the YARN Timeline Service > v2. But MR is legacy code and hence these changes could affect how users are > using these tags. > Add a note in mapred-default.xml > -------------------------------------------- > Add notes in the property name, mapreduce.job.tags mentioning that for > purposes of ATSv2, prefixes need to be added to the tag names. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org