[ http://issues.apache.org/jira/browse/HADOOP-195?page=comments#action_12378768 ]
Doug Cutting commented on HADOOP-195: ------------------------------------- By "map task creation" do you mean task startup costs? We have not yet explicitly measured that, but it does involve starting a JVM. Currently the shuffle is still the slowest step, and until that changes, that's where the attention is. Gigabyte blocks could prove useful. We have not yet experimented much with larger sized blocks. > transfer map output transfer with http instead of rpc > ----------------------------------------------------- > > Key: HADOOP-195 > URL: http://issues.apache.org/jira/browse/HADOOP-195 > Project: Hadoop > Type: Improvement > Components: mapred > Versions: 0.2 > Reporter: Owen O'Malley > Assignee: Owen O'Malley > Fix For: 0.3 > Attachments: netstat.log, netstat.xls > > The data transfer of the map output should be transfered via http instead > rpc, because rpc is very slow for this application and the timeout behavior > is suboptimal. (server sends data and client ignores it because it took more > than 10 seconds to be received.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
