[
https://issues.apache.org/jira/browse/HDDS-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846930#comment-16846930
]
Hudson commented on HDDS-1535:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16595 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16595/])
HDDS-1535. Space tracking for Open Containers : Handle Node Startup. (sdeka:
rev 869a1ab41a7c817e3f5f9bb5c74a93b68e5d2af4)
* (edit)
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/ozoneimpl/ContainerReader.java
* (edit)
hadoop-hdds/container-service/src/test/java/org/apache/hadoop/ozone/container/ozoneimpl/TestOzoneContainer.java
> Space tracking for Open Containers : Handle Node Startup
> --------------------------------------------------------
>
> Key: HDDS-1535
> URL: https://issues.apache.org/jira/browse/HDDS-1535
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: Ozone Datanode
> Reporter: Supratim Deka
> Assignee: Supratim Deka
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> This is related to HDDS-1511
> Space tracking for Open Containers (committed space in the volume) relies on
> usedBytes in the Container state. usedBytes is not persisted for every update
> (chunkWrite). So on a node restart the value is stale.
> The proposal is to:
> iterate the block DB for each open container during startup and compute the
> used space.
> The block DB process will be accelerated by spawning executors for each
> container.
> This process will be carried out as part of building the container set during
> startup.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
