[
https://issues.apache.org/jira/browse/HBASE-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768085#comment-13768085
]
M. BagherEsmaeily commented on HBASE-9537:
------------------------------------------
I noticed that the following line is in Region server log, which causes copying
instead of cut:
"on different filesystem than destination store - moving to this filesystem."
This shows that source and destination store files are on different file
systems, but both of them are on same HDFS. I just want to know what is the
reason for this problem.
Thanks
> completebulkload does 'copy' StoreFiles instead of 'cut'
> --------------------------------------------------------
>
> Key: HBASE-9537
> URL: https://issues.apache.org/jira/browse/HBASE-9537
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 0.94.11
> Reporter: M. BagherEsmaeily
> Attachments: LoadIncrementalHFiles.log, region.log
>
>
> I was using HBase complete bulk load to transfer the output of ImportTsv to a
> table in HBase, and I noticed that it copies the output instead of cutting.
> This takes long time for my gigabytes of data.
> In HBase documentation
> (http://hbase.apache.org/book/ops_mgt.html#completebulkload) I read that the
> files would be moved not copied. Can anyone help me with this?
> I use Hbase 0.94.11 and Hadoop 1.2.1. The file system of bulkload output
> directory and hbase cluster are the same, too.
> I've also coded a MapReduce job using HFileOutputFormat. When I use
> LoadIncrementalHFiles to move the output of my job to HBase table, it still
> copies instead of cut.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
