[
https://issues.apache.org/jira/browse/HADOOP-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681446#action_12681446
]
Hairong Kuang commented on HADOOP-5465:
---------------------------------------
>This implies that all the blocks that remained under replicated have only one
>replica and only on this specific datanode. Was that the case?
Yes, most of the blocks have only one source. Those are the kind of blocks that
initially triggers a DataNode into this state. But we could and our clusters do
have under-replicated blocks that have two replicas and all its sources are in
this state. The only exception is a block in our clusters that has two sources,
one in this state but the other is replicating. This block is still under
investigation.
> Blocks remain under-replicated
> ------------------------------
>
> Key: HADOOP-5465
> URL: https://issues.apache.org/jira/browse/HADOOP-5465
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.3
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Priority: Blocker
> Fix For: 0.18.4
>
> Attachments: xmitsSync1.patch
>
>
> Occasionally we see some blocks remain to be under-replicated in our
> production clusters. This is what we obeserved:
> 1. Sometimes when increasing the replication factor of a file, some blocks
> belonged to this file do not get to increase to the new replication factor.
> 2. When taking meta save in two different days, some blocks remain in
> under-replication queue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
