[jira] [Commented] (OOZIE-2258) Introducing a new counter in the instrumentation log to distinguish between the reasons for launcher failure

["Jaydeep Vishwakarma (JIRA)" <ji...@apache.org>]

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

Jaydeep Vishwakarma commented on OOZIE-2258:
--------------------------------------------

Looks like you have left some debug message as sysout. 
Same code added two places for adding counter  , Better to put some flag and use that flag to set the counter. 

> Introducing a new counter in the instrumentation log to distinguish between the reasons for launcher failure
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-2258
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2258
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: Narayan Periwal
>            Assignee: Narayan Periwal
>         Attachments: OOZIE-2258-v0.patch
>
>
> Whether the launcher job fails due to child job failure or exception in the launcher job itself, in both the case, the "counters:jobs:killed" counter is updated in the instrumentation log. Hence, we cannot distinguish whether the launcher failure was due to child job getting failed or not. So, we can introduce a new counter "kill" under the group "childjobs" that will help us to distinguish if the launcher failure is due to the child jobs getting failed.
> Let me know if there is already any other way by which we can distinguish this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)