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

Hudson commented on HDDS-140:
-----------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14547 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/14547/])
HDDS-140. Add DU usage to VolumeInfo. (hanishakoneru: rev 
772c95395b59dc9db61fa8f3721a6c81f97a1f4d)
* (add) 
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/impl/VolumeUsage.java
* (edit) 
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/impl/RoundRobinVolumeChoosingPolicy.java
* (edit) 
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/impl/VolumeSet.java
* (edit) 
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/impl/VolumeInfo.java
* (edit) 
hadoop-hdds/container-service/src/test/java/org/apache/hadoop/ozone/container/common/interfaces/TestVolumeSet.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/fsdataset/VolumeChoosingPolicy.java


> Add DU usage to VolumeInfo
> --------------------------
>
>                 Key: HDDS-140
>                 URL: https://issues.apache.org/jira/browse/HDDS-140
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-140-HDDS-48.001.patch, HDDS-140-HDDS-48.002.patch
>
>
> We need to start a DU thread per VolumeInfo to get the usage info.
> Each VolumeInfo object will wrap a VolumeUsage object to collect usage info.
> The proposed VolumeUsage class will replace ContainerStorageLocation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to