[
https://issues.apache.org/jira/browse/HDFS-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Isaacson updated HDFS-3902:
--------------------------------
Attachment: hdfs3902.txt
Due to HDFS-1371, the {{IOUtils.copyBytes}} in testBlockCorruptionPolicy does
not report a fully corrupt block as corrupt, so testBlockCorruptionPolicy has
been broken for a long time. The breakage was hidden by the overly fast
rescanning in HDFS-3828.
In order to fix this, Todd suggested we should directly run the block scanner
on each DN, which requires some straightforward tooling
(DataNodeTestUtils#runBlockScannerForBlock and a few @VisibleForTesting
annotations).
After this patch, TestDatanodeBlockScanner still fails about 1/5 runs in
testBlockCorruptionRecoveryPolicy2. That's due to a separate test issue also
uncovered by HDFS-3828.
> TestDatanodeBlockScanner is flaky, broke entirely after HDFS-3828
> -----------------------------------------------------------------
>
> Key: HDFS-3902
> URL: https://issues.apache.org/jira/browse/HDFS-3902
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha
> Reporter: Andy Isaacson
> Assignee: Andy Isaacson
> Priority: Minor
> Attachments: hdfs3902.txt
>
>
> Since HDFS-3828 fixed the block scanner to not repeatedly rescan small
> blockpools, TestDatanodeBlockScanner times out after 13 minutes in
> {{waitReplication}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
