hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5912) Document exit codes and their meanings used by linux task controller
Date Thu, 10 Dec 2009 10:16:19 GMT

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

Vinod K V commented on HADOOP-5912:
-----------------------------------

bq. Can you elaborate on the issue as well as why a documentation bug is a blocker ? 
On linux, for the sake of security and for running the tasks as the user themselves, TaskTracker
uses LinuxTaskController binary. This can err out in various scenarious and the exit codes
reflect the reason for failure. Currently the binary has a lot of exit codes(see _src/c++/task-controller/task-controller.h_),
each signifying a particular type of error, but the exit codes are not yet documented. This
issue should address this.

It is usual around here to fix documentation bugs as blockers as they won't add any new feature
per se.

> Document exit codes and their meanings used by linux task controller
> --------------------------------------------------------------------
>
>                 Key: HADOOP-5912
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5912
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Sreekanth Ramakrishnan
>            Priority: Blocker
>             Fix For: 0.21.0
>
>
> Currently, linux task controller binary uses a set of exit code, which is not documented.
These should be documented.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message