hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elton Tian (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2396) InMemFSMergeThread.doInMemMerge() miss the last MapOutput for each merge round
Date Tue, 05 Apr 2011 04:42:05 GMT

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

Elton Tian updated MAPREDUCE-2396:
----------------------------------

    Summary: InMemFSMergeThread.doInMemMerge() miss the last MapOutput for each merge round
   (was: InMemFSMergeThread.doInMemMerge() miss the lass MapOutput for each merge round  )

> InMemFSMergeThread.doInMemMerge() miss the last MapOutput for each merge round  
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2396
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2396
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.20.2
>            Reporter: Elton Tian
>            Priority: Critical
>
> In ReduceTask.shuffleInMemory(), once a new MapOutput is read, the ramManager.closeInMemoryFile()
is called to notify waitForDataToMerge()  to check if a in memory merge is required. If the
threshold is met, the doInMemMerge() may start before the MapOutput just read been added to
mapOutputsFilesInMemory. So the "dataAvailable.notify();" should be removed and let the noteCopiedMapOutput()
notify the merge. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message