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

Arpit Agarwal commented on HDFS-7824:
-------------------------------------

The tests pass for me locally but Jenkins flagged some exceptions in 
getContentSummary.

{code}
org/apache/hadoop/fs/ContentSummary$Builder
 at 
org.apache.hadoop.hdfs.server.namenode.INode.computeAndConvertContentSummary(INode.java:447)
 at 
org.apache.hadoop.hdfs.server.namenode.INode.computeContentSummary(INode.java:436)
 at 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.convertLastBlockToUnderConstruction(BlockManager.java:747)
 at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.prepareFileForAppend(FSNamesystem.java:2698)
 at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.appendFileInternal(FSNamesystem.java:2661)
 at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.appendFileInt(FSNamesystem.java:2943)
 at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.appendFile(FSNamesystem.java:2914)
 at 
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.append(NameNodeRpcServer.java:656)
{code}

> GetContentSummary API and its namenode implementaion for Storage Type 
> Quota/Usage
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-7824
>                 URL: https://issues.apache.org/jira/browse/HDFS-7824
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>         Attachments: HDFS-7824.00.patch, HDFS-7824.01.patch, 
> HDFS-7824.02.patch, HDFS-7824.03.patch
>
>
> This JIRA is opened to provide API support of GetContentSummary with storage 
> type quota and usage information. It includes namenode implementation, client 
> namenode RPC protocol and Content.Counts refactoring. It is required by 
> HDFS-7701 (CLI to display storage type quota and usage).



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

Reply via email to