[
https://issues.apache.org/jira/browse/HDFS-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masatake Iwasaki updated HDFS-1172:
-----------------------------------
Attachment: HDFS-1172.008.patch
I rebased the patch on current trunk and attached as HDFS-1172.008.patch.
* I added calling {{BlockManagerTestUtil#computeAllPendingWork}} in
{{TestReplication#pendingReplicationCount}} to make sure that replication is
scheduled. This is needed for the
{{TestReplication#testNoExtraReplicationWhenBlockReceivedIsLate}} to fail
without the fix of BlockManager.
* {{TestReplication#testReplicationWhenBlockCorruption}} succeeds without the
fix of BlockManager but I left it in the patch because there is no equivalent
test in the TestReplication.
> Blocks in newly completed files are considered under-replicated too quickly
> ---------------------------------------------------------------------------
>
> Key: HDFS-1172
> URL: https://issues.apache.org/jira/browse/HDFS-1172
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Attachments: HDFS-1172-150907.patch, HDFS-1172.008.patch,
> HDFS-1172.patch, hdfs-1172.txt, hdfs-1172.txt, replicateBlocksFUC.patch,
> replicateBlocksFUC1.patch, replicateBlocksFUC1.patch
>
>
> I've seen this for a long time, and imagine it's a known issue, but couldn't
> find an existing JIRA. It often happens that we see the NN schedule
> replication on the last block of files very quickly after they're completed,
> before the other DNs in the pipeline have a chance to report the new block.
> This results in a lot of extra replication work on the cluster, as we
> replicate the block and then end up with multiple excess replicas which are
> very quickly deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
