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

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on OOZIE-2258:
----------------------------------

Testing JIRA OOZIE-2258

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 132
.    {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2579/

> 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, OOZIE-2258-v1.patch, OOZIE-2258-v2.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)