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 DE9CC200B98 for ; Mon, 3 Oct 2016 23:45:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DD6F7160ADC; Mon, 3 Oct 2016 21:45:22 +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 5AA06160ACD for ; Mon, 3 Oct 2016 23:45:22 +0200 (CEST) Received: (qmail 7450 invoked by uid 500); 3 Oct 2016 21:45:21 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 7099 invoked by uid 99); 3 Oct 2016 21:45:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Oct 2016 21:45:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C10E72C2ABF for ; Mon, 3 Oct 2016 21:45:20 +0000 (UTC) Date: Mon, 3 Oct 2016 21:45:20 +0000 (UTC) From: "Suraj Acharya (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-13669) KMS Server should log exceptions before throwing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 03 Oct 2016 21:45:23 -0000 [ https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543524#comment-15543524 ] Suraj Acharya commented on HADOOP-13669: ---------------------------------------- I agree with the logic of it being a bit too much. However, my thought process was that since most of these errors will be a fatal error (either killing the operation in progress / killing the startup of the KMS) i thought it was worth putting this as an error message. But ill take whatever recommendation you'll give me on this one. > KMS Server should log exceptions before throwing > ------------------------------------------------ > > Key: HADOOP-13669 > URL: https://issues.apache.org/jira/browse/HADOOP-13669 > Project: Hadoop Common > Issue Type: Improvement > Components: kms > Reporter: Xiao Chen > Assignee: Suraj Acharya > Labels: supportability > Attachments: HADOOP-13369.patch > > > In some recent investigation, it turns out when KMS throws an exception (into tomcat), it's not logged anywhere and we can only see the exception message from client-side, but not the stacktrace. Logging the stacktrance would help debugging. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org