incubator-oozie-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Idris Ali <psychid...@gmail.com>
Subject Re: External Id for action of type MR
Date Fri, 27 Apr 2012 15:31:29 GMT
Thanks Mona,

I was trying to copy Task-Tracker logs locally of oozie:launcher.

-Idris

On Thu, Apr 26, 2012 at 11:18 PM, Mona Chitnis <chitnis@yahoo-inc.com>wrote:

> Hi Idris,
>
> Yes this is by design. For workflows having java/pig actions, the launcher
> mapper stays as a pointer to the actions and oozie job progress is tracked
> with launcher’s status. For MR action, however, once the launcher mapper
> launches the action, the oozie job uses the action’s MR job-id for tracking
> progress.
>
> Do you have any use-case surrounding this question?
>
> Thanks,
>
> Mona
>
>
> On 4/26/12 7:23 AM, "Idris Ali" <psychidris@gmail.com> wrote:
>
> Hi,
>
> For workflow actions of type Java and Pig; I see that oozie sets external
> id to hadoop job id, which is actually oozie:launcher.
> However, for action of type MR; oozie sets hadoop job id to oozie:action.
>
> Is it by design?
> Thanks,
> -Idris
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message