You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Huang Guan Hao (Jira)" <ji...@apache.org> on 2025/12/06 02:35:00 UTC
[jira] [Commented] (HDDS-13922) Increase available space requirement during pipeline/container allocation
[ https://issues.apache.org/jira/browse/HDDS-13922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043197#comment-18043197 ]
Huang Guan Hao commented on HDDS-13922:
---------------------------------------
[~siddhant] Ok, thanks, I'll update the patch.
> Increase available space requirement during pipeline/container allocation
> -------------------------------------------------------------------------
>
> Key: HDDS-13922
> URL: https://issues.apache.org/jira/browse/HDDS-13922
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Reporter: Siddhant Sangwan
> Assignee: Huang Guan Hao
> Priority: Major
> Labels: pull-request-available
>
> Currently we use "ozone.scm.container.size" (5GB default) in various implementations of PipelineProvider and in ContainerManagerImpl#getMatchingContainer when checking if a DN has enough disk space for a container.
> The problem is that if only 6 GB is remaining, this check will return true concurrently for multiple clients. But there's only space for 1 container, leading to container creation failures for all but 1 client. So we should increase this space requirement to a multiple of container size.
--
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