[jira] [Updated] (HDFS-8402) Fsck exit codes are not reliable
[ https://issues.apache.org/jira/browse/HDFS-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated HDFS-8402: -- Target Version/s: (was: 2.7.3) Dropping 2.7.x target-version till the above compatibility discussion closes. > 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) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-8402) Fsck exit codes are not reliable
[ https://issues.apache.org/jira/browse/HDFS-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated HDFS-8402: -- Target Version/s: 2.7.3 (was: 2.7.2) Moving out all non-critical / non-blocker issues that didn't make it out of 2.7.2 into 2.7.3. > 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)
[jira] [Updated] (HDFS-8402) Fsck exit codes are not reliable
[ https://issues.apache.org/jira/browse/HDFS-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated HDFS-8402: -- Release Note: A block-based report will emit a final line similar to a path-based report: Some checked block replicas are CORRUPT All checked block replicas are HEALTHY 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)
[jira] [Updated] (HDFS-8402) Fsck exit codes are not reliable
[
https://issues.apache.org/jira/browse/HDFS-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HDFS-8402:
--
Attachment: HDFS-8402.patch
Prior to blockId checking, ie. path based scans, fsck determined exit code
based on whether the last line contained HEALTHY or CORRUPT. This doesn't make
sense when displaying multiple blocks with multiple storages. Modified NN's
blockid scans to return a final line similar to path-based scans. Removed the
recent logic that flagged nodes with decom nodes as an error.
The real motivation for this patch is to use {{bm.getStorages(block)}} instead
of directly accessing the storages. This altered the order of the storages,
which broke the tests. The tests were specifically coded (grumble) to ensure
the last displayed storage was in the state expected by the test.
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)
[jira] [Updated] (HDFS-8402) Fsck exit codes are not reliable
[ https://issues.apache.org/jira/browse/HDFS-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated HDFS-8402: -- Status: Patch Available (was: Open) 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)
[jira] [Updated] (HDFS-8402) Fsck exit codes are not reliable
[ https://issues.apache.org/jira/browse/HDFS-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-8402: --- Hadoop Flags: Incompatible change Marking this as incompatible as per compatibility guidelines, as it changes the output of fsck. 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)
