hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-2465) Add HDFS support for fadvise readahead and drop-behind
Date Fri, 28 Oct 2011 22:22:32 GMT

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

Todd Lipcon updated HDFS-2465:
------------------------------

       Resolution: Fixed
    Fix Version/s: 0.23.0
     Release Note: 
HDFS now has the ability to use posix_fadvise and sync_data_range syscalls to manage the OS
buffer cache. This support is currently considered experimental, and may be enabled by configuring
the following keys:
dfs.datanode.drop.cache.behind.writes - set to true to drop data out of the buffer cache after
writing
dfs.datanode.drop.cache.behind.reads - set to true to drop data out of the buffer cache when
performing sequential reads
dfs.datanode.sync.behind.writes - set to true to trigger dirty page writeback immediately
after writing data
dfs.datanode.readahead.bytes - set to a non-zero value to trigger readahead for sequential
reads
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Committed to trunk and 23. Thanks for the review, Eli.
                
> Add HDFS support for fadvise readahead and drop-behind
> ------------------------------------------------------
>
>                 Key: HDFS-2465
>                 URL: https://issues.apache.org/jira/browse/HDFS-2465
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node, performance
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.23.0
>
>         Attachments: hdfs-2465.txt, hdfs-2465.txt, hdfs-2465.txt, hdfs-2465.txt
>
>
> This is the HDFS side of HADOOP-7714. The initial implementation is heuristic based and
should be considered experimental, as discussed in the parent JIRA. It should be off by default
until better heuristics, APIs, and tuning experience is developed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message