You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Vinay (JIRA)" <ji...@apache.org> on 2013/11/22 04:04:35 UTC

[jira] [Commented] (HDFS-5549) Support for implementing custom FsDatasetSpi from outside the project

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

Vinay commented on HDFS-5549:
-----------------------------

Hi [~icorderi],
May I know the usecases of this improvement.?

You want to change the Datanode to datanode block transfer to some other implementation?

> Support for implementing custom FsDatasetSpi from outside the project
> ---------------------------------------------------------------------
>
>                 Key: HDFS-5549
>                 URL: https://issues.apache.org/jira/browse/HDFS-5549
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 3.0.0
>            Reporter: Ignacio Corderi
>         Attachments: HDFS-5549.patch
>
>
> Visibility for multiple methods and a few classes got changed to public to allow FsDatasetSpi<T> and all the related classes that need subtyping to be fully implemented from outside the HDFS project.
> Blocks transfers got abstracted to a factory given that the behavior will be changed for DataNodes using Kinetic drives. The existing DataNode to DataNode block transfer functionality got moved to LegacyBlockTransferer, no new configuration is needed to use this class and have the same behavior that is currently present.
> DataNodes have an additional configuration key DFS_DATANODE_BLOCKTRANSFERER_FACTORY_KEY to override the default block transfer behavior.



--
This message was sent by Atlassian JIRA
(v6.1#6144)