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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/05/02 06:30:09 UTC
[jira] [Commented] (HADOOP-9733) a node's stack trace output to log
file should be controllable
[ https://issues.apache.org/jira/browse/HADOOP-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524653#comment-14524653 ]
Hadoop QA commented on HADOOP-9733:
-----------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12599759/HADOOP-9733.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/6284/console |
This message was automatically generated.
> a node's stack trace output to log file should be controllable
> --------------------------------------------------------------
>
> Key: HADOOP-9733
> URL: https://issues.apache.org/jira/browse/HADOOP-9733
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Shinichi Yamashita
> Priority: Minor
> Attachments: HADOOP-9733.patch
>
>
> We can confirm the stack trace of node when we access the node's web interface "/stacks".
> And the stack trace is output not only browser but also log file of node.
> Considering the cluster's management policy (e.g. log monitoring), it should be controllable.
> At now implementation, stack trace output controls HttpServer class.
> If we change log level, other messages does not output by HttpServer class.
> So, we control to output the stacktrace to log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)