hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Trezzo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8789) Block Placement policy migrator
Date Mon, 08 May 2017 17:50:05 GMT

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

Chris Trezzo commented on HDFS-8789:

[~kihwal] Thanks for the comment! As I said, this is just a strawman and is no where near
ready for commit. I just posted it as a starting point for conversation. I.e. where should
the functionality of block placement policy migration be supported and what are some high
level approaches people would be interested in?

I can see four options off the top of my head for supporting block placement policy:
1. Client side
2. Namenode
3. Additional server side daemon
4. No where (i.e. we leave it up to users to build their own tools)

> Block Placement policy migrator
> -------------------------------
>                 Key: HDFS-8789
>                 URL: https://issues.apache.org/jira/browse/HDFS-8789
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>            Reporter: Chris Trezzo
>            Assignee: Chris Trezzo
>         Attachments: HDFS-8789-trunk-STRAWMAN-v1.patch
> As we start to add new block placement policies to HDFS, it will be necessary to have
a robust tool that can migrate HDFS blocks between placement policies. This jira is for the
design and implementation of that tool.

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