You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2012/06/13 03:35:43 UTC
[jira] [Updated] (HDFS-3228) Use fadvise in local read path
[ https://issues.apache.org/jira/browse/HDFS-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HDFS-3228:
------------------------------
Comment: was deleted
(was: Integrated in Hadoop-Hdfs-trunk-Commit #2423 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2423/])
Amendment to my previous commit, fixing JIRA in CHANGES.txt from HDFS-3228 to HDFS-3428 (Revision 1349556)
Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1349556
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
)
> Use fadvise in local read path
> ------------------------------
>
> Key: HDFS-3228
> URL: https://issues.apache.org/jira/browse/HDFS-3228
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs client, performance
> Reporter: Henry Robinson
> Assignee: Henry Robinson
>
> The read path through BlockReaderLocal does not take advantage of readahead or drop-behind in the way that BlockSender does. We could arguably stand to gain even more from hinting about read patterns to the kernel here, so we should add the same mechanisms to BlockReaderLocal.
--
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