hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5465) Blocks remain under-replicated
Date Thu, 12 Mar 2009 20:46:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681483#action_12681483

Hairong Kuang commented on HADOOP-5465:

> I thought there would be very few datanodes hitting such a race condition. 
On a cluster with thousands of machines, we saw 5% of the nodes were 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. 
It turns out that the other source that is replicating has a corrupt copy of the block.

> 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, 0.19.2, 0.20.0, 0.21.0
>         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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message