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] [Commented] (HDFS-9083) Replication violates block placement policy.
Date Tue, 27 Oct 2015 20:15:27 GMT

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

Jing Zhao commented on HDFS-9083:
---------------------------------

The patch looks good to me. [~mingma] and [~brahmareddy], do you also want to take a look
at the patch since you guys worked on HDFS-8647.

> Replication violates block placement policy.
> --------------------------------------------
>
>                 Key: HDFS-9083
>                 URL: https://issues.apache.org/jira/browse/HDFS-9083
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: HDFS, namenode
>    Affects Versions: 2.6.0
>            Reporter: Rushabh S Shah
>            Assignee: Rushabh S Shah
>            Priority: Blocker
>         Attachments: HDFS-9083-branch-2.7.patch
>
>
> Recently we are noticing many cases in which all the replica of the block are residing
on the same rack.
> During the block creation, the block placement policy was honored.
> But after node failure event in some specific manner, the block ends up in such state.
> On investigating more I found out that BlockManager#blockHasEnoughRacks is dependent
on the config (net.topology.script.file.name)
> {noformat}
>  if (!this.shouldCheckForEnoughRacks) {
>       return true;
>     }
> {noformat}
> We specify DNSToSwitchMapping implementation (our own custom implementation) via net.topology.node.switch.mapping.impl
and no longer use net.topology.script.file.name config.



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

Mime
View raw message