You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Daniel Templeton (JIRA)" <ji...@apache.org> on 2015/09/02 18:53:46 UTC

[jira] [Resolved] (HDFS-8989) Allow rate-limiting the DirectoryScanner via time-slicing

     [ https://issues.apache.org/jira/browse/HDFS-8989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Templeton resolved HDFS-8989.
------------------------------------
    Resolution: Duplicate

This is the same issue as HDFS-8873 as far as I can see.  I'll add the salient details from the description as a comment there.

> Allow rate-limiting the DirectoryScanner via time-slicing
> ---------------------------------------------------------
>
>                 Key: HDFS-8989
>                 URL: https://issues.apache.org/jira/browse/HDFS-8989
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 2.0.6-alpha
>            Reporter: Colin Patrick McCabe
>            Assignee: Daniel Templeton
>
> When the inodes and directory entries for HDFS block and meta files are not in the cache, the DirectoryScanner can create enormous disk load via generating many seeks.  This can effectively make the disks unusable for other purposes.  We should allow rate-limiting the DirectoryScanner via time-slicing, so that it only runs every 100 ms out of 1 s (or whatever other percentage we configure.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)