hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3452) fsck exit code would be better if non-zero when FS corrupt
Date Thu, 29 May 2008 12:44:45 GMT

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

Steve Loughran commented on HADOOP-3452:

-Error codes could be something added as an option. They are reliable, except that proxy servers
like to interfere.

-moving to constants should be easy.

It would be extra impressive if the result was hidden in a <span> with a specific name,
so you could XPATH/regexp on the response and look for <span class="status" >SUCCESS</span>
through some Xpath like


>Do you have another mechanism in mind (other than using a servlet) to run fsck?

Possibly. In SVN we have the code to bring up any of the name/data/tracker/jobtracker nodes
and execute operations on the filesystem,  though many more tests are needed. adding an FSCK
check component would round things off. Right now, I'd consider generating an httpclient request
with all the parameters and do a regexp search on the result. 

> fsck exit code would be better if non-zero when FS corrupt
> ----------------------------------------------------------
>                 Key: HADOOP-3452
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3452
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Pete Wyckoff
>            Priority: Minor
>             Fix For: 0.18.0
>         Attachments: HADOOP-3452-1.patch
> fsck exit code would be better if behaved like other sys admin tools and exit code indicated
healthy/corrupt or other  errors.

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

View raw message