hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8402) Fsck exit codes are not reliable
Date Mon, 18 May 2015 19:09:01 GMT

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

Daryn Sharp commented on HDFS-8402:
-----------------------------------

I'm unclear if you are blocking this patch?  I feel it's a bit hardline to deem a bug fix
for a new feature in 2.7.0 as incompatible.  Would you prefer if I ignore the bug and just
hack the test to make it pass again?  If no, what are my options to move forward?

> 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
(v6.3.4#6332)

Mime
View raw message