Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 5 May 2011 03:38:03 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1178540655.23555.1304566683132.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <255568256.57875.1302794345991.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-3782) Multi-Family support for bulk
 upload tools causes File Not Found Exception
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029115#comment-13029115 ] 

Aaron T. Myers commented on HBASE-3782:
---------------------------------------

I took a look into this. From what I can tell, I believe Nichole's patch modifies the original patch which was posted on HBASE-1861, i.e. {{HBASE1861-incomplete.patch}}. However, what ended up getting committed to resolve HBASE-1861 differs substantially from that original patch. So, I'm pretty confident that this problem isn't applicable to what ended up getting committed.

Nichole, can you confirm this?

> Multi-Family support for bulk upload tools causes File Not Found Exception
> --------------------------------------------------------------------------
>
>                 Key: HBASE-3782
>                 URL: https://issues.apache.org/jira/browse/HBASE-3782
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 0.90.3
>            Reporter: Nichole Treadway
>         Attachments: HBASE-3782.patch
>
>
> I've been testing HBASE-1861 in 0.90.2, which adds multi-family support for bulk upload tools.
> I found that when running the importtsv program, some reduce tasks fail with a File Not Found exception if there are no keys in the input data which fall into the region assigned to that reduce task.  From what I can determine, it seems that an output directory is created in the write() method and expected to exist in the writeMetaData() method...if there are no keys to be written for that reduce task, the write method is never called and the output directory is never created, but writeMetaData is expecting the output directory to exist...thus the FnF exception:
> 2011-03-17 11:52:48,095 WARN org.apache.hadoop.mapred.TaskTracker: Error running child
> java.io.FileNotFoundException: File does not exist: hdfs://master:9000/awardsData/_temporary/_attempt_201103151859_0066_r_000000_0
> 	at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:468)
> 	at org.apache.hadoop.hbase.regionserver.StoreFile.getUniqueFile(StoreFile.java:580)
> 	at org.apache.hadoop.hbase.mapreduce.HFileOutputFormat$1.writeMetaData(HFileOutputFormat.java:186)
> 	at org.apache.hadoop.hbase.mapreduce.HFileOutputFormat$1.close(HFileOutputFormat.java:247)
> 	at org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:567)
> 	at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:408)
> 	at org.apache.hadoop.mapred.Child.main(Child.java:170)
> Simply checking if the file exists should fix the issue. 

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