Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 77EE5185E8 for ; Sun, 13 Mar 2016 05:37:40 +0000 (UTC) Received: (qmail 11612 invoked by uid 500); 13 Mar 2016 05:37:40 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 11539 invoked by uid 500); 13 Mar 2016 05:37:40 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 11526 invoked by uid 99); 13 Mar 2016 05:37:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Mar 2016 05:37:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1649B2C14F4 for ; Sun, 13 Mar 2016 05:37:40 +0000 (UTC) Date: Sun, 13 Mar 2016 05:37:40 +0000 (UTC) From: "Li Lu (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MAPREDUCE-6110) JobHistoryServer CLI throws NullPointerException with job ids that do not exist MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192145#comment-15192145 ] Li Lu commented on MAPREDUCE-6110: ---------------------------------- Sure, will take a look at it soon... Sorry about the delay... > JobHistoryServer CLI throws NullPointerException with job ids that do not exist > ------------------------------------------------------------------------------- > > Key: MAPREDUCE-6110 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6110 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver > Reporter: Li Lu > Assignee: Kai Sasaki > Priority: Minor > Attachments: MAPREDUCE-6110.01.patch, MAPREDUCE-6110.02.patch > > > When using JobHistoryServer CLI to query a job id that does not exist on the server, it may throw NullPointerException sometimes. > I tried "mapred job -events 0 100", and the result was: > Exception in thread "main" java.lang.NullPointerException > at org.apache.hadoop.mapreduce.tools.CLI.listEvents(CLI.java:487) > at org.apache.hadoop.mapreduce.tools.CLI.run(CLI.java:316) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84) > at org.apache.hadoop.mapred.JobClient.main(JobClient.java:1237) > Similar symptoms also appear with -list-attempt-ids, but were fine with -status and -set-priority. > I traced back to CLI.listEvents, and line 487 is: > {code} > TaskCompletionEvent[] events = job. > getTaskCompletionEvents(fromEventId, numEvents); > {code} > The job object is obtained from JobID.forName(jobid)) (line 316), which will return null if the job does not exist on server. > Maybe we want to have some behaviors consistent with -status here, by simply reporting jobId does not exist? -- This message was sent by Atlassian JIRA (v6.3.4#6332)