incubator-oozie-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mona Chitnis <>
Subject Re: External Id for action of type MR
Date Thu, 26 Apr 2012 17:48:25 GMT
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?



On 4/26/12 7:23 AM, "Idris Ali" <> wrote:


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?

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