[
https://issues.apache.org/jira/browse/HDDS-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-12928:
----------------------------------
Labels: pull-request-available (was: )
> datanode min-free-space configuration as per disk capacity
> ----------------------------------------------------------
>
> Key: HDDS-12928
> URL: https://issues.apache.org/jira/browse/HDDS-12928
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Datanode
> Reporter: Sumit Agrawal
> Assignee: Sumit Agrawal
> Priority: Major
> Labels: pull-request-available
>
> Default Min Free Space for Ozone is 5GB, But based on disk size and usage,
> this seems not correct.
>
> *Configuration as Max of below can be used as Min Free Space:*
> # hdds.datanode.volume.min.free.space --> 5GB
> # hdds.datanode.volume.min.free.space.percent --> 0.1% or 0.001
>
> Single Disk configuration:
> |Disk Space in TB|Min Free Space (with percent as 1% or 0.01)|Min Free Space
> (with percent as 0.1% or 0.001)|
> |100 GB|5 GB (as min space)| 5GB (as min space)|
> |1 TB|10 GB|5GB (as min space)|
> |10 TB|100 GB|10 GB|
> |100 TB|1 TB|100 GB|
>
> Mostly I have seen 10-15TB as single disk being mounted, considering this,
> above can be both valid percent configurations which does not seem too high
> or too low value.
>
> So, MinFreeSpace = Max(free.space, free.space.percent)
>
> In my opinion, going with 0.1% (0.0001) to be appropriate as default value.
>
> Concern: ozone volume db size if big, then compaction activity may need
> equivalent free space to run properly.
> With going min-free-space as percent, will resolve the issue as
> min-free-space requirement increases with disk size / and in-turn number of
> container support.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
