You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Akshay Rai (JIRA)" <ji...@apache.org> on 2015/08/20 12:31:46 UTC

[jira] [Commented] (OOZIE-1658) Add bundle, coord, wf and action related information to launched M/R jobs.

    [ https://issues.apache.org/jira/browse/OOZIE-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704646#comment-14704646 ] 

Akshay Rai commented on OOZIE-1658:
-----------------------------------

Hi [~puru] and [~rohini],

Shouldn't enabling _oozie.action.jobinfo.enable_ inject the job information into the mapreduce job's configuration?

Steps I followed:
* Enabled the property _oozie.action.jobinfo.enable_ in oozie-site.xml.
* Restarted oozie.
* Ran a map-reduce job.

After following the above steps, I couldn't find the property _oozie.job.info_ in the job conf while accessing it from the jobhistory.

In the code, I noticed that before the method injectJobInfo(Class: {{JavaActionExecutor}}, Line: 1067) is called, the actionConf is already written to action.xml(Class: {{LauncherMapperHelper}}, Line: 156). The _createLauncherConf_ method which is called just before the _injectJobInfo_ method, internally calls _LauncherMapperHelper.setupLauncherInfo_ which writes the actionConf to _LauncherMapper.ACTION_CONF_XML_. I think we should set this property, _oozie.job.info_, before copying the actionConf to action.xml.

Please correct me if I am wrong.

> Add bundle, coord, wf and action related information to launched M/R jobs.
> --------------------------------------------------------------------------
>
>                 Key: OOZIE-1658
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1658
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Purshotam Shah
>            Assignee: Purshotam Shah
>             Fix For: 4.1.0
>
>         Attachments: OOZIE-1658-v1.patch, OOZIE-1658-v2.patch, OOZIE-1658.patch
>
>
> We should add workflow related information to launched job. This information can be used for analytics like how many oozie jobs are submitted for a particular period, what is the total number of failed pig jobs.. etc from mapreduce jobhistory logs and configuration.
> JobInfo will contain information of bundle, coordinator, workflow and actions. If enabled, Hadoop job will have
> property(oozie.job.info) which value is multiple key/value pair separated by ";". 
> User can also add custom workflow property to jobinfo by adding property which prefix with "oozie.job.info."
> Eg.
> oozie.job.info="bundle.id=;bundle.name=;coord.name=;coord.nominal.time=;coord.name=;wf.id=;
> wf.name=;action.name=;action.type=;launcher=true"
>  
> Jobinfo can enabled/disabled using "oozie.action.jobinfo.enable"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)