hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8404) Pending block replication can get stuck using older genstamp
Date Tue, 19 May 2015 18:07:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550907#comment-14550907
] 

Kihwal Lee commented on HDFS-8404:
----------------------------------

+1 the patch looks good. 

> Pending block replication can get stuck using older genstamp
> ------------------------------------------------------------
>
>                 Key: HDFS-8404
>                 URL: https://issues.apache.org/jira/browse/HDFS-8404
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.6.0, 2.7.0
>            Reporter: Nathan Roberts
>            Assignee: Nathan Roberts
>         Attachments: HDFS-8404-v0.patch, HDFS-8404-v1.patch
>
>
> If an under-replicated block gets into the pending-replication list, but later the  genstamp
of that block ends up being newer than the one originally submitted for replication, the block
will fail replication until the NN is restarted. 
> It will be safer if processPendingReplications()  gets up-to-date blockinfo before resubmitting
replication work.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message