[
https://issues.apache.org/jira/browse/HADOOP-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated HADOOP-2947:
--------------------------------------------
Attachment: HADOOP-2947
Attaching a patch. stdout and stderr are now saved along with hadoop.log in the
hadoop log directory. Thus, stdout is redirected to
$HADOOP_LOG_DIR/<daemon-name>.out and stderr to
$HADOOP_LOG_DIR/<daemon-name>.err.
Made changes to simpleCommand to enable starting commands with stderr and/or
stdout set. And made related changes in HadoopCommand.
Added testcases. Also tested by giving a sigquit to jobtracker and verifying
that the standard output indeed goes to the jobtracker.out file. Didn't get to
check stderr.
> [HOD] Hod should redirect stderr and stdout of Hadoop daemons to assist
> debugging
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-2947
> URL: https://issues.apache.org/jira/browse/HADOOP-2947
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/hod
> Affects Versions: 0.16.0
> Reporter: Hemanth Yamijala
> Assignee: Vinod Kumar Vavilapalli
> Fix For: 0.17.0
>
> Attachments: HADOOP-2947
>
>
> Copied from internal bug details from Koji:
> ==========================
> Sometimes JobTracker/TaskTracker starts consuming 99% cpu and stops
> responding to 'jstack' call. In those cases,
> usually it still responds to kill -QUIT signal which forces the jvm to dump
> the stack to stdout.
> Please have the stdout of JT/TT redirected to a file.
> Adding stderr.
> If thread has an uncaught exception, it prints out to stderr and dies.
> ==========================
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
