[
https://issues.apache.org/jira/browse/HADOOP-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601777#action_12601777
]
lohit vijayarenu commented on HADOOP-3452:
------------------------------------------
Thanks Steve, Dhruba for looking into this. If we consider the current
implmentation, fsck was implemented as servlet so that we do not use RPC. The
client opens up URL connection and reads the output from FSCK servlet. We might
not be able to set new headers/response code at the end of fsck executiong
since the fsck in itself take a while to complete. And the status is not know
prior to executing fsck. Could you brief me as to how we could get the response
other than scanning this stream?
> 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.
