[
https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15573022#comment-15573022
]
Wei-Chiu Chuang commented on HADOOP-13669:
------------------------------------------
Got it [~xiaochen]
The findbugs warning refers to trunk code, not the patch.
{quote}
cd /testptch/hadoop/hadoop-common-project/hadoop-kms
mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-trunk-patch-0 -Ptest-patch
-DskipTests test-compile findbugs:findbugs -DskipTests=true >
/testptch/hadoop/patchprocess/branch-findbugs-hadoop-common-project_hadoop-kms.txt
2>&1
Elapsed: 0m 23s
hadoop-common-project/hadoop-kms in trunk has 2 extant Findbugs warnings.
{quote}
So Yetus should not flag findbugs warning in trunk. Probably worth an
improvement.
+1 from me. I'll leave it untouched until EOB in case Allen has additional
comments.
> 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, HADOOP-13669.addendum.patch, trigger.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: [email protected]
For additional commands, e-mail: [email protected]
