hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8402) Fsck exit codes are not reliable
Date Tue, 15 Dec 2015 16:35:46 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058286#comment-15058286

Kihwal Lee commented on HDFS-8402:

The changes looks good, but it does not apply to trunk anymore. Can you refresh the patch?

> Fsck exit codes are not reliable
> --------------------------------
>                 Key: HDFS-8402
>                 URL: https://issues.apache.org/jira/browse/HDFS-8402
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.7.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>         Attachments: HDFS-8402.patch
> HDFS-6663 added the ability to check specific blocks.  The exit code is non-deterministically
based on the state (corrupt, healthy, etc) of the last displayed block's last storage location
- instead of whether any of the checked blocks' storages are corrupt.  Blocks with decommissioning
or decommissioned nodes should not be flagged as an error.

This message was sent by Atlassian JIRA

View raw message