hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13682) Log missing stacktrace in catch block
Date Tue, 04 Oct 2016 17:23:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15546035#comment-15546035
] 

Allen Wittenauer commented on HADOOP-13682:
-------------------------------------------

This sounds like it is going in the opposite direction.  In order to make Hadoop user friendly,
we should be eliminating stack traces, not generating more.

> Log missing stacktrace in catch block
> -------------------------------------
>
>                 Key: HADOOP-13682
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13682
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Wei-Chiu Chuang
>            Priority: Minor
>         Attachments: common_output
>
>
> Wrote a simple [code parser|https://github.com/jojochuang/codebetter] to find all instances
of exception objects that are caught but logged without stack trace. Some of them may have
legitimate reason not to log stack trace, but other may worth an improvement.



--
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


Mime
View raw message