hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashwin Shankar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4927) Historyserver 500 error due to NPE when accessing specific counters page for failed job
Date Thu, 16 May 2013 22:47:16 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ashwin Shankar updated MAPREDUCE-4927:
--------------------------------------

    Attachment: MAPREDUCE-4927.txt

The problem is that a failed task doesn't have counters and we assume that we always get counters
which causes an NPE. I've added a null check for counters to fix this. Also I've changed a
unit test to incorporate this case.
                
> Historyserver 500 error due to NPE when accessing specific counters page for failed job
> ---------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4927
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4927
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver
>    Affects Versions: 2.0.3-alpha, 0.23.6
>            Reporter: Jason Lowe
>         Attachments: MAPREDUCE-4927.txt
>
>
> Went to the historyserver page for a job that failed and examined the counters page.
 When I clicked on a specific counter, the historyserver returned a 500 error.  The historyserver
logs showed it encountered an NPE error, full traceback to follow.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message