[ https://issues.apache.org/jira/browse/HDFS-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549120#comment-14549120 ]
Allen Wittenauer commented on HDFS-8402: ---------------------------------------- Nope, I'm not blocking the patch. I just want clarity in release notes, etc. in case someone stumbles upon this later because it broke stuff. As a community, we've clearly thrown backward compatibility for ops under a huge bus so it doesn't really matter if this goes into a branch-2 or not. > 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)