You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Sumit Agrawal (Jira)" <ji...@apache.org> on 2025/07/07 05:58:00 UTC
[jira] [Resolved] (HDDS-12929) Datanode Should Immediately Trigger Container Close when Volume Full
[ https://issues.apache.org/jira/browse/HDDS-12929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sumit Agrawal resolved HDDS-12929.
----------------------------------
Fix Version/s: 2.1.0
Resolution: Fixed
> Datanode Should Immediately Trigger Container Close when Volume Full
> --------------------------------------------------------------------
>
> Key: HDDS-12929
> URL: https://issues.apache.org/jira/browse/HDDS-12929
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Datanode
> Reporter: Sumit Agrawal
> Assignee: Siddhant Sangwan
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.1.0
>
>
> SCM keeps allocating blocks till DN reports that the container is full. This is limitation as:
> * Blocks as written can be small like 1 KB to high as 256MB, so can not identify number of blocks at SCM
> * Communication from DN to SCM is every 30 seconds, and report handling at SCM may take time, so container size can not be guaranteed to be reported immediately.
>
> *An improvement is possible,*
> *ICR* for Container Close action, this can be reported more immediately.
>
> This will reduce the impact of write operation being rejected due to disk fail situation.
--
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