hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9535) Newly completed blocks in IBR should not be considered under-replicated too quickly
Date Mon, 14 Dec 2015 19:24:46 GMT

     [ https://issues.apache.org/jira/browse/HDFS-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jing Zhao updated HDFS-9535:
----------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.8.0
           Status: Resolved  (was: Patch Available)

I've committed the patch into trunk, branch-2, and branch-2.8.

> Newly completed blocks in IBR should not be considered under-replicated too quickly
> -----------------------------------------------------------------------------------
>
>                 Key: HDFS-9535
>                 URL: https://issues.apache.org/jira/browse/HDFS-9535
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.8.0
>            Reporter: Jing Zhao
>            Assignee: Mingliang Liu
>             Fix For: 2.8.0
>
>         Attachments: HDFS-9535.000.patch, HDFS-9535.001.patch, HDFS-9535.002.patch
>
>
> TestReplication#testNoExtraReplicationWhenBlockReceivedIsLate failed in several Jenkins
run (e.g., https://builds.apache.org/job/PreCommit-HDFS-Build/13818/testReport/). The failure
is on the last {{assertNoReplicationWasPerformed}} check.
> This test failure reveals a scenario that HDFS-1172 missed: if a block is first committed
by the client, and then the first IBR comes to the NN, as proposed by HDFS-1172, we should
still put the remaining expected replicas into the pending queue, instead of the under-replicated
queue. Please see [~liuml07]'s comment [here|https://issues.apache.org/jira/browse/HDFS-9535?focusedCommentId=15052397&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15052397]
for more details.



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

Mime
View raw message