[
https://issues.apache.org/jira/browse/HDFS-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164070#comment-13164070
]
Uma Maheswara Rao G commented on HDFS-1765:
-------------------------------------------
{quote}-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics
{quote}
Failure should not be due to this patch. Without this patch also it is failing
locally for me.
After deleting the file it is checking for Underreplicated blocks count to be
0. That will be updated once DN updates about delete. This is handled in
testFileAdd. Same added for this test also.
> Block Replication should respect under-replication block priority
> -----------------------------------------------------------------
>
> Key: HDFS-1765
> URL: https://issues.apache.org/jira/browse/HDFS-1765
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.24.0
>
> Attachments: HDFS-1765.patch, HDFS-1765.patch, HDFS-1765.pdf,
> underReplicatedQueue.pdf
>
>
> Currently under-replicated blocks are assigned different priorities depending
> on how many replicas a block has. However the replication monitor works on
> blocks in a round-robin fashion. So the newly added high priority blocks
> won't get replicated until all low-priority blocks are done. One example is
> that on decommissioning datanode WebUI we often observe that "blocks with
> only decommissioning replicas" do not get scheduled to replicate before other
> blocks, so risking data availability if the node is shutdown for repair
> before decommission completes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
