[
https://issues.apache.org/jira/browse/HBASE-16257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503034#comment-15503034
]
Ashish Singhi commented on HBASE-16257:
---------------------------------------
Your thinking is correct, HFileReplicator is using the staging dir configured
on the sink cluster. It is getting the staging dir path from the sink cluster
conf. If the staging dir doesn't exist it will create it and copy the HFiles
from the source cluster to the sink cluster staging dir and then run the
complete bulkload tool.
> Move staging dir to be under hbase root dir
> -------------------------------------------
>
> Key: HBASE-16257
> URL: https://issues.apache.org/jira/browse/HBASE-16257
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jerry He
> Assignee: Jerry He
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-16257-v1.patch, HBASE-16257-v2.patch,
> HBASE-16257-v3.patch, HBASE-16257-v4.patch
>
>
> The hbase.bulkload.staging.dir defaults to hbase.fs.tmp.dir which then
> defaults to
> {code}
> public static final String DEFAULT_TEMPORARY_HDFS_DIRECTORY = "/user/"
> + System.getProperty("user.name") + "/hbase-staging";
> {code}
> This default would have problem on local file system standalone case.
> We can move the staging dir to be under hbase.rootdir. We are bringing
> secure bulkload to the core. It makes sense to bring it under core control as
> well, instead of an optional property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
