Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A3227200CEF for ; Mon, 4 Sep 2017 16:12:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A1C5F165104; Mon, 4 Sep 2017 14:12:09 +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 E95D7165105 for ; Mon, 4 Sep 2017 16:12:08 +0200 (CEST) Received: (qmail 93666 invoked by uid 500); 4 Sep 2017 14:12:08 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 93651 invoked by uid 99); 4 Sep 2017 14:12:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Sep 2017 14:12:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 8BD201A28D0 for ; Mon, 4 Sep 2017 14:12:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id GJRFdI6ChX2t for ; Mon, 4 Sep 2017 14:12:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 4F66F5FD48 for ; Mon, 4 Sep 2017 14:12:02 +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 2923EE09A5 for ; Mon, 4 Sep 2017 14:12:01 +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 47B392415B for ; Mon, 4 Sep 2017 14:12:00 +0000 (UTC) Date: Mon, 4 Sep 2017 14:12:00 +0000 (UTC) From: "Jinjiang Ling (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7128) The error message in TimelineSchemaCreator is not enough to find out the error. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 04 Sep 2017 14:12:09 -0000 [ https://issues.apache.org/jira/browse/YARN-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152650#comment-16152650 ] Jinjiang Ling commented on YARN-7128: ------------------------------------- [~vrushalic], thanks for your review. The warning in prechecks is that the patch doesn't appear to include any new or modified tests. I think it is not necessory to update tests in it. > The error message in TimelineSchemaCreator is not enough to find out the error. > ------------------------------------------------------------------------------- > > Key: YARN-7128 > URL: https://issues.apache.org/jira/browse/YARN-7128 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Affects Versions: 3.0.0-beta1 > Reporter: Jinjiang Ling > Assignee: Jinjiang Ling > Attachments: YARN-7128.patch > > > When I run the schema creator tool of timeline service v2, then an error happened with the error message below: > {quote} > 17/08/30 16:04:18 INFO zookeeper.ClientCnxn: Session establishment complete on server zdh175/10.43.183.175:2181, sessionid = 0x15e0d065a330019, negotiated timeout = 180000 > 17/08/30 16:04:18 WARN util.HeapMemorySizeUtil: hbase.regionserver.global.memstore.upperLimit is deprecated by hbase.regionserver.global.memstore.size > 17/08/30 16:04:18 ERROR storage.TimelineSchemaCreator: Error in creating hbase tables: java.lang.reflect.InvocationTargetException > 17/08/30 16:04:18 WARN storage.TimelineSchemaCreator: Schema creation finished with the following exceptions > 17/08/30 16:04:18 WARN storage.TimelineSchemaCreator: java.lang.reflect.InvocationTargetException > {quote} > But I can't tell which error caused this exception with message. > Then I find it only print the exception message in TimelineSchemaCreator > {code} > try { > ...... > } catch (IOException e) { > LOG.error("Error in creating hbase tables: " + e.getMessage()); > exceptions.add(e); > } > {code} > I change it like this > {code} > try { > ...... > } catch (IOException e) { > LOG.error("Error in creating hbase tables: ", e); > exceptions.add(e); > } > {code} > finally, I get the detail of this error, and it's caused by a directory of hbase not created. > {quote} > at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:648) > ... 10 more > Caused by: java.lang.RuntimeException: Failed to create local dir /data1/zdh/hbase/tmp/RegionServer/local/jars, DynamicClassLoader failed to init > at org.apache.hadoop.hbase.util.DynamicClassLoader.initTempDir(DynamicClassLoader.java:110) > at org.apache.hadoop.hbase.util.DynamicClassLoader.(DynamicClassLoader.java:98) > at org.apache.hadoop.hbase.protobuf.ProtobufUtil.(ProtobufUtil.java:244) > ... 15 more > 17/08/30 16:03:42 WARN storage.TimelineSchemaCreator: Schema creation finished with the following exceptions > 17/08/30 16:03:42 WARN storage.TimelineSchemaCreator: java.lang.reflect.InvocationTargetException > {quote} > As the exception message is not enough to find out the error, so I think print all the information of the exception in TimelineSchemaCreator is better. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org