hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Virajith Jalaparti (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12893) [READ] Support replication of Provided blocks with non-default topologies.
Date Fri, 08 Dec 2017 18:31:00 GMT

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

Virajith Jalaparti commented on HDFS-12893:

bq. You are pretty much just copying the storage. 

Yes. that was intention -- to ensure that going forward, this is treated as a regular {{DatanodeStorageInfo}}
which has only one {{DatanodeDescriptor}} associated with it.

I don't think creating a new subtype is required just to replace this. We already have the
{{ProvidedDatanodeStorageInfo}} that is a subclass of {{DatanodeStorageInfo}} but only one
instance of that exists and it is shared by all {{DatanodeDescriptor}}s that have PROVIDED

> [READ] Support replication of Provided blocks with non-default topologies.
> --------------------------------------------------------------------------
>                 Key: HDFS-12893
>                 URL: https://issues.apache.org/jira/browse/HDFS-12893
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Virajith Jalaparti
>            Assignee: Virajith Jalaparti
>         Attachments: HDFS-12893-HDFS-9806.001.patch, HDFS-12893-HDFS-9806.002.patch,
> {{chooseSourceDatanodes}} returns the {{ProvidedDatanodeDescriptor}} as the source of
Provided blocks. As this isn't a physical datanode and doesn't exist the topology, {{ReplicationWork.chooseTargets}}
might fail depending on the chosen {{BlockPlacementPolicy}} implementation. This JIRA aims
to fix this issue.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message