[ 
https://issues.apache.org/jira/browse/HDFS-13283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459180#comment-16459180
 ] 

Íñigo Goiri commented on HDFS-13283:
------------------------------------

Thanks [~lukmajercak] for the patches and [~chris.douglas] and [~virajith] for 
the reviews.
Committed all the way to 2.9: turnk, branch-3.1, branch-3.0, branch-2, and 
branch-2.9.

> Percentage based Reserved Space Calculation for DataNode
> --------------------------------------------------------
>
>                 Key: HDFS-13283
>                 URL: https://issues.apache.org/jira/browse/HDFS-13283
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: datanode, hdfs
>            Reporter: Lukas Majercak
>            Assignee: Lukas Majercak
>            Priority: Major
>             Fix For: 2.10.0, 3.2.0, 3.1.1, 2.9.2, 3.0.4
>
>         Attachments: HDFS-13283.000.patch, HDFS-13283.001.patch, 
> HDFS-13283.002.patch, HDFS-13283.003.patch, HDFS-13283.004.patch, 
> HDFS-13283.005.patch, HDFS-13283.006.patch, HDFS-13283.007.patch, 
> HDFS-13283_branch-2.000.patch, HDFS-13283_branch-3.0.000.patch
>
>
> Currently, the only way to configure reserved disk space for non-HDFS data on 
> a DataNode is a constant value via {{dfs.datanode.du.reserved}}. This can be 
> an issue in non-heterogeneous clusters where size of DNs can differ. The 
> proposed solution is to allow percentage based configuration (and their 
> combination):
>  # ABSOLUTE
>  ** based on absolute number of reserved space
>  # PERCENTAGE
>  ** based on percentage of total capacity in the storage
>  # CONSERVATIVE
>  ** calculates both of the above and takes the one that will yield more 
> reserved space
>  # AGGRESSIVE
>  ** calculates 1. 2. and takes the one that will yield less reserved space
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to