You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Peter Cseh (JIRA)" <ji...@apache.org> on 2018/03/29 11:43:00 UTC

[jira] [Commented] (OOZIE-3203) Oozie web console - links to job

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

Peter Cseh commented on OOZIE-3203:
-----------------------------------

Thanks for filing this jira!
This is an interesting change, I'll have to take a deep dive into the git logs to figure out what happened.

> Oozie web console - links to job
> --------------------------------
>
>                 Key: OOZIE-3203
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3203
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 4.3.0
>            Reporter: Łukasz
>            Priority: Minor
>         Attachments: Selection_002.png
>
>
> In oozie web console there is a option to go to yarn job that is associated with current oozie action (see image).
> I have the situation that luncher starts new job:
> _Submitting Oozie action Map-Reduce job_
> _=======================_ 
> _<<< Invocation of Main class completed_ 
> _<<< Oozie Launcher, propagating new Hadoop job id to Oozie_ 
> _======================= job_1522069947629_0148 =======================_ 
> _Oozie Launcher, uploading action data to HDFS sequence file: hdfs://n1/user/hadoop/oozie-hado/0000055-180326153118810-oozie-hado-W/createPhraseIndex--map-reduce/action-data.seq_ 
> _Successfully reset security manager from org.apache.oozie.action.hadoop.LauncherSecurityManager@5d5e780d to null_ 
> _Oozie Launcher ends_
> Launcher started new job and new id was propagated to Oozie, but after this link in web console is not updated i.e. link from web console still directs to luncher action, not the actual job.
> In version 3.3, I was using previously, links in web console where updated after Launcher finished.
> Can this behavior be restored, because right now it it necessary  to manually look for job in yarn console to control logs and counter of the action.
> Thank you in advance.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)