You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Mukund Madhugiri (JIRA)" <ji...@apache.org> on 2008/06/07 03:26:46 UTC
[jira] Updated: (HADOOP-3356) SequenceFile.MergeQueue.merge
inadvertently creates merge-outputs in the wrong FileSystem, at times in
the InMemoryFileSystem
[ https://issues.apache.org/jira/browse/HADOOP-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mukund Madhugiri updated HADOOP-3356:
-------------------------------------
Fix Version/s: (was: 0.18.0)
> SequenceFile.MergeQueue.merge inadvertently creates merge-outputs in the wrong FileSystem, at times in the InMemoryFileSystem
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3356
> URL: https://issues.apache.org/jira/browse/HADOOP-3356
> Project: Hadoop Core
> Issue Type: Bug
> Components: io
> Affects Versions: 0.16.3
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Priority: Minor
>
> The offending code is:
> {code:title=SequenceFile.java}
> Path outputFile = lDirAlloc.getLocalPathForWrite(
> tmpFilename.toString(),
> approxOutputSize, conf);
> LOG.debug("writing intermediate results to " + outputFile);
> Writer writer = cloneFileAttributes(
> fs.makeQualified(segmentsToMerge.get(0).segmentPathName),
> fs.makeQualified(outputFile), null);
> {code}
> *fs* is InMemoryFileSystem when ReduceTask.ReduceCopier constructs it... so the wrong FileSystem is used during intermediate merges.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.