Hi, Sorry for spam, but I think I just figured it out. It's look like Oozie treats SSH action not like the MapReduce so it isn't put this type of action in JobTracker and I can't see logs through Oozie Web Console. I created shell action that performs command: ssh user@host 'shell_command' And now Oozie treats it as MR - everything looks fine, on the JobTracker I can see this job, logs are available through Oozie Web Console (or job history). Of course, I had to provide passwordless ssh between YARN clients on the all nodes.
Best regards, Rafal Trzcinski 2014-10-20 11:52 GMT+02:00 Rafał Trzciński <[email protected]>: > Hi, > > Is there some progress with my issue that I send You some time ago? I'm > still have the same problem. Thank you for help. > There is Stackoverflow link below, where I describe this issue: > > http://stackoverflow.com/questions/25259364/oozie-ssh-action-job-is-not-shown-in-jobhistory-and-jobtracker-dag-visualizatio > > Best regards, > Rafal Trzcinski > > 2014-08-25 10:08 GMT+02:00 Rafał Trzciński <[email protected]>: > >> Hi Everyone, >> >> Sorry for mailing, but I have got problem with Oozie and I had looking >> everywhere. Maybe it's bug in Oozie and it could be issue but first I want >> to ask You. More probably is something wrong with configuration. Could You >> help me with this problem, please? >> >> I created Oozie workflow with ssh action. >> Code of workflow.xml definition: >> >> <workflow-app name="ssh-test" xmlns="uri:oozie:workflow:0.4"> >> <start to="ssh_test"/> >> <action name="ssh_test"> >> <ssh xmlns="uri:oozie:ssh-action:0.1"> >> <host>rtrzcinski@hdw2dn1</host> >> <command>ls</command> >> <capture-output/> >> </ssh> >> <ok to="end"/> >> <error to="kill"/> >> </action> >> <kill name="kill"> >> <message>"Killed job due to error"</message> >> </kill> >> <end name="end"/> >> </workflow-app> >> >> I run WF by command: >> >> oozie job -config conf.xml -run >> >> where conf.xml is XML file in my local directory: >> >> >> <?xml version="1.0" encoding="UTF-8" standalone="no"?> >> <configuration> >> <property> >> <name>nameNode</name> >> <value>hdfs://hdw2nn1:8020</value> >> </property> >> <property> >> <name>jobTracker</name> >> <value>hdw2nn1:8050</value> >> </property> >> <property> >> <name>oozie.wf.application.path</name> >> >> <value>hdfs://hdw2nn1:8020/user/rtrzcinski/home/rtrzcinski/workspaces/shell_test/workflow.xml</value> >> </property> >> <property> >> <name>oozie.use.system.libpath</name> >> <value>true</value> >> </property> >> </configuration> >> >> And everything is fine, job is finished with succeeded status. One thing is >> not normal is that I cannot see logs from Oozie Web Services: >> 1) Job History: http://hdw2nn1:19888/jobhistory/app >> >> There is not present record with that oozie job >> >> 2) Job Tracker: http://hdw2nn1:8088/cluster >> >> Same as above - there are not present information about that oozie job >> >> When I run Oozie WF with shell action - information about this is job is >> available in Job History and Job Tracker. >> >> 3) In Oozie Web console, consoleURL, trackerURI and extenral ID generate >> wrong values. >> >> >> I attached screenshot (image1.jpg) where You can see, that tihs values are >> strange, beacuese I can't >> >> access to web url's (when I click this little loupe icon REST not response). >> >> Correct URL's are shown in second attached file (image2.jpg). >> >> I can see files .stdout, .stderr, .pid in my local directory. Catalog >> /oozie-oozi/JOB_ID is created and there are all files. The issue >> is that I want to see this logs by Oozie Web Console or Job Tracker or Job >> History. >> >> I will be gratefull for help. >> >> >> Rafal Trzcinski >> >> >> >
