Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 7 May 2012 11:09:54 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <921088851.33855.1336388994577.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2098850065.8065.1333482742804.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-4102) job counters not available in
 Jobhistory webui for killed jobs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on MAPREDUCE-4102:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12525828/MAPREDUCE-4102.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 2 new or modified test files.

    -1 javadoc.  The javadoc tool appears to have generated 2 warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    -1 findbugs.  The patch appears to cause Findbugs (version 1.3.9) to fail.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

    +1 core tests.  The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2360//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2360//console

This message is automatically generated.
                
> job counters not available in Jobhistory webui for killed jobs
> --------------------------------------------------------------
>
>                 Key: MAPREDUCE-4102
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4102
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: webapps
>    Affects Versions: 0.23.2, 2.0.0
>            Reporter: Thomas Graves
>         Attachments: MAPREDUCE-4102-1.patch, MAPREDUCE-4102.patch, MAPREDUCE-4102.patch
>
>
> Run a simple wordcount or sleep, and kill the job before it finishes.  Go to the job history web ui and click the "Counters" link for that job. It displays "500 error".
> The job history log has:
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 2012-04-03 19:42:53,148 ERROR org.apache.hadoop.yarn.webapp.Dispatcher: error handling URI: /jobhistory/jobcounters/job_1333482028750_0001
> java.lang.reflect.InvocationTargetException
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:597)
> ...
> ..
> ...
> 1) Error injecting constructor, java.lang.NullPointerException
>   at org.apache.hadoop.mapreduce.v2.app.webapp.CountersBlock.<init>(CountersBlock.java:56)
>   while locating org.apache.hadoop.mapreduce.v2.app.webapp.CountersBlock
> ...
> ..
> ...
> Caused by: java.lang.NullPointerException    at org.apache.hadoop.mapreduce.counters.AbstractCounters.incrAllCounters(AbstractCounters.java:328)
>     at org.apache.hadoop.mapreduce.v2.app.webapp.CountersBlock.getCounters(CountersBlock.java:188)
>     at org.apache.hadoop.mapreduce.v2.app.webapp.CountersBlock.<init>(CountersBlock.java:57)
>     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> There are task counters available if you drill down into successful tasks though.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira