[jira] [Resolved] (HDDS-12419) Space tracking for Imported Containers in HDDS Volumes

["Ethan Rose (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-12419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Rose resolved HDDS-12419.
-------------------------------
    Resolution: Duplicate

> Space tracking for Imported Containers in HDDS Volumes
> ------------------------------------------------------
>
>                 Key: HDDS-12419
>                 URL: https://issues.apache.org/jira/browse/HDDS-12419
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Sammi Chen
>            Assignee: Chia-Chuan Yu
>            Priority: Major
>
> Multiple container imports can happen in parallel.  There is enough free space(2 *5GB) check when datanode choose which volume to download and import container. But this multiple container imports in parallel, the free space check is not enough. 
> In "HDDS-1511. Space tracking for Open Containers in HDDS Volumes", it introduced a *committedBytes* field to reflect the reserved 5GB space for a new open container. Its  value will be adjusted when the container is closed.  *committedBytes* is treated as allocated from Datanode and SCM's perspective. 
> We can adopt the same idea here for container import, reserving a 2 * 5GB space using *committedBytes*, and removing(or adjust) the reserving after container import is finished, to avoid over allocation of space for parallel container imports. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org