- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
oozie shell action
- Labels:
-
Apache Oozie
Created 03-05-2019 02:54 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I created a similar job as in : https://community.hortonworks.com/content/supportkb/48985/how-to-setup-oozie-shell-action.html
On execution the yarn log shows as success.
But I can't see the /tmp/output file being created anywhere. I checked on the local linux host as well as hdfs.
One question I have is in job.properties -
oozie.coord.application.path=${nameNode}/user/root/apps/shell
Should the configuration files (job.properties, coordinator.xml etc) reside in the above directory? I have them there.
Not sure what is happening.
Appreciate the insights.
Created 03-08-2019 06:33 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
job.properties -> Needs to be on local filesystem on Oozie client from where you wish to submit the oozie job -run command. No need to have this file on HDFS.
workflow.xml -> This needs to be on HDFS.
script -> This needs to be on HDFS.
Regarding your question on python script - Please refer below article for how to create coordinator ( Please ignore input event part )
in coordinator.xml you mention "<app-path>${workflowAppUri}</app-path>" that's what is location of workflow.xml
Please use Ambari workflow manager to design coordinators and workflows with easy WebUI.
Hope this helps.
Please let me know if you have any questions. Please accept my answer if it was helpful. 🙂
Created 03-05-2019 06:18 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In the yarn log for the job I can see :
=================================================================
>>> Invoking Shell command line now >>
Exit code of the Shell command 0
<<< Invocation of Shell command completed <<<
<<< Invocation of Main class completed <<<
Oozie Launcher, capturing output data:
=======================
Created 03-06-2019 07:01 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @n c
Can you please check on the node manager where this launcher was run, ideally this file should be created locally on the node manager where your shell script was run.
Please do let me know if you need any further help.
Created 03-06-2019 07:01 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Kuldeep Kulkarni , any insights pls? Appreciate the help.
Created 03-06-2019 07:10 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>this file should be created locally on the node manager where your shell script was run
I have the file locally on a node. It is on this node that I execute the oozie command.
Are you saying that the shell script should be in hdfs? And that yarn will execute this shell script on the node manager on which this job was run? Rather than on the host from which I run the oozie command?
Appreciate the feedback.
Created 03-06-2019 07:21 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yes, I checked the nodes and found the output in one of them. I reran to make sure.
So the script is not really needed on the Linux box? all of them - job.properties, the shellscript, workflow.xml, coordinator.xml? They need to be only in hdfs?
Also next, how to execute a python code from oozie? Also I want it to run daily.
Appreciate the insights.
Created 03-08-2019 02:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Kuldeep Kulkarni, I created python action based on https://community.hortonworks.com/content/supportkb/151119/how-to-run-a-python-script-using-oozie-sh...
But how do I integrate coordinator.xml with that?
I tried creating the file but it is not executing as per that.
Is there somewhere in job.properties or workflow.xml that you mention coordinator.xml?
Appreciate the feedback.
Created 03-08-2019 06:33 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
job.properties -> Needs to be on local filesystem on Oozie client from where you wish to submit the oozie job -run command. No need to have this file on HDFS.
workflow.xml -> This needs to be on HDFS.
script -> This needs to be on HDFS.
Regarding your question on python script - Please refer below article for how to create coordinator ( Please ignore input event part )
in coordinator.xml you mention "<app-path>${workflowAppUri}</app-path>" that's what is location of workflow.xml
Please use Ambari workflow manager to design coordinators and workflows with easy WebUI.
Hope this helps.
Please let me know if you have any questions. Please accept my answer if it was helpful. 🙂
Created 03-08-2019 06:58 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Kuldeep, thanks so much for the clarification.
I will try to do as per your instructions and let you know how it went.
Thanks again.
Created 03-08-2019 06:59 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
BTW now I use cloudera. So I guess it has to be manual. Thanks.
