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 2015/05/06 05:34:41 UTC

[jira] [Updated] (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:all-tabpanel ]

Allen Wittenauer updated HADOOP-9733:
-------------------------------------
    Labels: BB2015-05-TBR  (was: )

> 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
>              Labels: BB2015-05-TBR
>         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)