You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Xiaoyu Yao (JIRA)" <ji...@apache.org> on 2015/05/27 01:51:18 UTC
[jira] [Resolved] (HDFS-8465) Mover is success even when space
exceeds storage quota.
[ https://issues.apache.org/jira/browse/HDFS-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoyu Yao resolved HDFS-8465.
------------------------------
Resolution: Not A Problem
Thanks [~szetszwo] for providing the context information about Mover. [~archanat], I'm resolving this issue as by design. Let me know if you think it differently.
> Mover is success even when space exceeds storage quota.
> -------------------------------------------------------
>
> Key: HDFS-8465
> URL: https://issues.apache.org/jira/browse/HDFS-8465
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer & mover, namenode
> Affects Versions: 2.7.0
> Reporter: Archana T
> Assignee: surendra singh lilhore
> Labels: QBST
>
> *Steps :*
> 1. Create directory /dir
> 2. Set its storage policy to HOT --
> hdfs storagepolicies -setStoragePolicy -path /dir -policy HOT
> 3. Insert files of total size 10,000B into /dir.
> 4. Set above path "/dir" ARCHIVE type quota to 5,000B --
> hdfs dfsadmin -setSpaceQuota 5000 -storageType ARCHIVE /dir
> {code}
> hdfs dfs -count -v -q -h -t /dir
> DISK_QUOTA REM_DISK_QUOTA SSD_QUOTA REM_SSD_QUOTA ARCHIVE_QUOTA REM_ARCHIVE_QUOTA PATHNAME
> none inf none inf 4.9 K 4.9 K /dir
> {code}
> 5. Now change policy of '/dir' to COLD
> 6. Execute Mover command
> *Observations:*
> 1. Mover is successful moving all 10,000B to ARCHIVE datapath.
> 2. Count command displays negative value '-59.4K'--
> {code}
> hdfs dfs -count -v -q -h -t /dir
> DISK_QUOTA REM_DISK_QUOTA SSD_QUOTA REM_SSD_QUOTA ARCHIVE_QUOTA REM_ARCHIVE_QUOTA PATHNAME
> none inf none inf 4.9 K -59.4 K /dir
> {code}
> *Expected:*
> Mover should not be successful as ARCHIVE quota is only 5,000B.
> Negative value should not be displayed for quota output.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)