[ https://issues.apache.org/jira/browse/MAPREDUCE-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427726#comment-13427726 ]
Hudson commented on MAPREDUCE-3289: ----------------------------------- Integrated in Hadoop-Hdfs-trunk-Commit #2617 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2617/]) MAPREDUCE-3289. Make use of fadvise in the NM's shuffle handler. (Contributed by Todd Lipcon and Siddharth Seth) (Revision 1368718) Result = SUCCESS sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1368718 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/FadvisedChunkedFile.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/FadvisedFileRegion.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java > Make use of fadvise in the NM's shuffle handler > ----------------------------------------------- > > Key: MAPREDUCE-3289 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3289 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mrv2, nodemanager, performance > Affects Versions: 0.23.0 > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Fix For: 1.2.0, 2.2.0-alpha > > Attachments: 3289-1.txt, 3289-2.txt, MAPREDUCE-3289.branch-1.patch, > MAPREDUCE-3289.branch-1.patch, MR3289_trunk.txt, MR3289_trunk_2.txt, > MR3289_trunk_3.txt, mr-3289.txt > > > Using the new NativeIO fadvise functions, we can make the NodeManager > prefetch map output before it's send over the socket, and drop it out of the > fs cache once it's been sent (since it's very rare for an output to have to > be re-sent). This improves IO efficiency and reduces cache pollution. -- 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