[
https://issues.apache.org/jira/browse/HDDS-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G resolved HDDS-6577.
---------------------------------------
Fix Version/s: 1.3.0
Resolution: Fixed
> Configurations to reserve HDDS volume space are not followed
> ------------------------------------------------------------
>
> Key: HDDS-6577
> URL: https://issues.apache.org/jira/browse/HDDS-6577
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode, SCM
> Reporter: Ethan Rose
> Assignee: Aswin Shakil Balasubramanian
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.3.0
>
>
> Ozone currently has two configuration keys that can be used to prevent
> datanode volumes from being completely filled up:
> hdds.datanode.du.reserved: A list of key-value pairs mapping each volume's
> path to a fixed size that should be left empty on the volume. There is no
> default value.
> hdds.datanode.storage.utilization.critical.threshold: A percentage of each
> datanode volume that should be left empty. The default value is 95%.
> In a live cluster, we have seen volumes fill up past the default 95% value.
> In a docker based test using a fixed size tmpfs volume mount, the configs
> also did not seem to be respected. It is also unclear how the configs are
> reconciled if configured with conflicting values. This Jira aims to provide a
> reliable way to limit datanode volume usage, and add tests to simulate fixed
> capacity disks for testing the functionality.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
