hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7159) Use block storage policy to set lazy persist preference
Date Tue, 30 Sep 2014 00:03:07 GMT

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

Tsz Wo Nicholas Sze commented on HDFS-7159:

bq. For now the feature will not be used unless the administrator explicitly configures RAM
disk in DataNode configuration. For 2.6 we are looking at integrating with the dfs.datanode.max.locked.memory
setting. So if that setting is not configured the feature would not be available. Sound okay?

Sound good.  What will happen if a user creates a file using the LAZY_PERSIST CreateFlag?

+1 the new patch looks good.

> Use block storage policy to set lazy persist preference
> -------------------------------------------------------
>                 Key: HDFS-7159
>                 URL: https://issues.apache.org/jira/browse/HDFS-7159
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>         Attachments: HDFS-7159.01.patch, HDFS-7159.02.patch, HDFS-7159.03.patch
> Now that HDFS-6584 feature is ready and supports block storage policies on both files
and directories, we can make use of Storage Policies to store the LAZY_PERSIST preference.
> This only affects how the preference is persisted in the FsImage/Edit logs. There is
no change to the client API or to NN-DN interaction.
> An additional advantage is that can support setting the lazy persist preference on a
directory and it will take effect for all new files.

This message was sent by Atlassian JIRA

View raw message