You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/05/13 08:48:00 UTC
[jira] [Updated] (HDDS-5209) Datanode hasEnoughSpace check should
apply on volume instead of global DN
[ https://issues.apache.org/jira/browse/HDDS-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-5209:
---------------------------------
Labels: pull-request-available (was: )
> Datanode hasEnoughSpace check should apply on volume instead of global DN
> -------------------------------------------------------------------------
>
> Key: HDDS-5209
> URL: https://issues.apache.org/jira/browse/HDDS-5209
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Sammi Chen
> Assignee: Mark Gui
> Priority: Major
> Labels: pull-request-available
>
> During Container replication, Replication manager is responsible for choose the DN to place the new replica. When a DN is choose, it's total remaning space is compared with the container used bytes. This will cause write problem when the DN total remaning space is greater than container used bytes, while none of the volumes of DN has enough space to hold the new container replica.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org