From mapreduce-issues-return-91042-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Feb 2 15:22:05 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 9309A180608 for ; Fri, 2 Feb 2018 15:22:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 81DED160C41; Fri, 2 Feb 2018 14:22:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CA005160C49 for ; Fri, 2 Feb 2018 15:22:04 +0100 (CET) Received: (qmail 28520 invoked by uid 500); 2 Feb 2018 14:22:03 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 28509 invoked by uid 99); 2 Feb 2018 14:22:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2018 14:22:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 64568C1AC4 for ; Fri, 2 Feb 2018 14:22:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id yD564zpdjspm for ; Fri, 2 Feb 2018 14:22:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id B7D255FAC2 for ; Fri, 2 Feb 2018 14:22:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D18C8E030C for ; Fri, 2 Feb 2018 14:22:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 42CDC21E87 for ; Fri, 2 Feb 2018 14:22:00 +0000 (UTC) Date: Fri, 2 Feb 2018 14:22:00 +0000 (UTC) From: "Peter Bacsko (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MAPREDUCE-7046) Enhance logging related to retrieving Job 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-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated MAPREDUCE-7046: ------------------------------------ Attachment: MAPREDUCE-7046-001.patch > Enhance logging related to retrieving Job > ----------------------------------------- > > Key: MAPREDUCE-7046 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7046 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: client > Reporter: Peter Bacsko > Assignee: Peter Bacsko > Priority: Major > Attachments: MAPREDUCE-7046-001.patch > > > We recently encountered an interesting problem. In one case, Hive Driver was unable to retrieve the status of a MapReduce job. The following stack trace was printed: > {noformat} > [main] INFO org.apache.hadoop.hive.ql.exec.Task - 2018-01-15 00:18:09,324 Stage-2 map = 0%, reduce = 0%, Cumulative CPU 1679.31 sec > [main] ERROR org.apache.hadoop.hive.ql.exec.Task - Ended Job = job_1511036412170_1322169 with exception 'java.io.IOException(Could not find status of job:job_1511036412170_1322169)' > java.io.IOException: Could not find status of job:job_1511036412170_1322169 > at org.apache.hadoop.hive.ql.exec.mr.HadoopJobExecHelper.progress(HadoopJobExecHelper.java:295) > at org.apache.hadoop.hive.ql.exec.mr.HadoopJobExecHelper.progress(HadoopJobExecHelper.java:549) > at org.apache.hadoop.hive.ql.exec.mr.ExecDriver.execute(ExecDriver.java:435) > at org.apache.hadoop.hive.ql.exec.mr.MapRedTask.execute(MapRedTask.java:137) > at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160) > at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:100) > at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1782) > at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1539) > at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1318) > at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1127) > at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1115) > at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:220) > at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:172) > at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:383) > at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:318) > at org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:416) > at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:432) > at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:726) > at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:693) > at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:628) > at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:325) > at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:302) > at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:49) > {noformat} > We examined the logs from JHS and AM, but haven't seen anything suspicious. For some reason a {{null}} was returned but it's not obvious why. The MR job was running at this point. > Some ideas: > 1. We already have logging in place related to JobClient->AM and JobClient->JHS communication, but that's on TRACE level and that could be too low. It might make more sense to raise the level to DEBUG. > 2. We need new {{LOG.debug()}} calls at some crucial points -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org