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-8805) Archival Storage: getStoragePolicy should not need superuser privilege
Date Tue, 11 Aug 2015 17:24:45 GMT

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

Jing Zhao commented on HDFS-8805:
---------------------------------

Thanks for updating the patch, [~brahmareddy]. +1 for the 004 patch. I will commit it shortly.

> Archival Storage: getStoragePolicy should not need superuser privilege
> ----------------------------------------------------------------------
>
>                 Key: HDFS-8805
>                 URL: https://issues.apache.org/jira/browse/HDFS-8805
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: balancer & mover, namenode
>            Reporter: Hui Zheng
>            Assignee: Brahma Reddy Battula
>             Fix For: 2.6.0
>
>         Attachments: HDFS-8805-002.patch, HDFS-8805-003.patch, HDFS-8805-004.patch, HDFS-8805.patch
>
>
> The result of getStoragePolicy command is always 'unspecified' even we has set a StoragePolicy
on a directory.But the real placement of blocks is correct. 
> The result of fsck is not correct either.
> {code}
> $ hdfs storagepolicies -setStoragePolicy -path /tmp/cold  -policy COLD
> Set storage policy COLD on /tmp/cold
> $ hdfs storagepolicies -getStoragePolicy -path /tmp/cold
> The storage policy of /tmp/cold is unspecified
> $ hdfs fsck -storagepolicies /tmp/cold
> Blocks NOT satisfying the specified storage policy:
> Storage Policy                  Specified Storage Policy      # of blocks       % of
blocks
> ARCHIVE:4(COLD)                     HOT                           5              55.5556%
> ARCHIVE:3(COLD)                     HOT                           4              44.4444%
> {code}



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

Mime
View raw message