[ https://issues.apache.org/jira/browse/HDFS-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145139#comment-14145139 ]
Colin Patrick McCabe commented on HDFS-6988: -------------------------------------------- It seems like these configuration keys should be longs, not ints, since we might want values bigger than 2 gigabytes. This scheme seems to be getting a little too complex to easily understand. Rather than having three configuration keys (min, max, percentage), how about a single configuration key that is interpreted differently based on its value? So if it is "10%" (has a percent sign at the end) we interpret it as a percentage... if it's "128MB" we interpret that as the amount of space to keep free. > Add configurable limit for percentage-based eviction threshold > -------------------------------------------------------------- > > Key: HDFS-6988 > URL: https://issues.apache.org/jira/browse/HDFS-6988 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: datanode > Affects Versions: HDFS-6581 > Reporter: Arpit Agarwal > Assignee: Arpit Agarwal > Fix For: HDFS-6581 > > Attachments: HDFS-6988.01.patch, HDFS-6988.02.patch > > > Per feedback from [~cmccabe] on HDFS-6930, we can make the eviction > thresholds configurable. The hard-coded thresholds may not be appropriate for > very large RAM disks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)