You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2016/10/12 16:49:21 UTC
[jira] [Reopened] (HADOOP-13669) KMS Server should log exceptions
before throwing
[ https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer reopened HADOOP-13669:
---------------------------------------
bq. Findbugs warnings are false alarm, since the exception is thrown.
...
bq. Committed this to trunk, branch-2 and branch-2.8.
Re-opening, because this patch needs an addendum. Please don't commit patches that throw findbugs errors.
If you are sure this is a false alarm, an exception must get added to findbugs-exclude.xml. Until that happens, the release, the nightlies, and all other patches against hadoop-kms are going to fail.
> 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
> Fix For: 2.8.0, 3.0.0-alpha2
>
> Attachments: HADOOP-13369.2.patch, HADOOP-13369.patch, HADOOP-13369.patch.1
>
>
> 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