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

Hudson commented on HBASE-21445:
--------------------------------

Results for branch master
        [build #596 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/596/]: (x) 
*{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/596//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/596//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/596//JDK8_Nightly_Build_Report_(Hadoop3)/]


(x) {color:red}-1 source release artifact{color}
-- See build output for details.


(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console 
output|https://builds.apache.org/job/HBase%20Nightly/job/master/596//console].


> CopyTable by bulkload will write hfile into yarn's HDFS 
> --------------------------------------------------------
>
>                 Key: HBASE-21445
>                 URL: https://issues.apache.org/jira/browse/HBASE-21445
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>            Reporter: Zheng Hu
>            Assignee: Zheng Hu
>            Priority: Major
>             Fix For: 1.5.0, 1.3.3, 2.2.0, 2.0.3, 1.4.9, 2.1.2, 1.2.9
>
>         Attachments: HBASE-21445.v1.patch
>
>
> When using CopyTable with bulkload, I found that all hfile's are written in 
> our Yarn's HDFS cluster.   and failed to load hfiles into HBase cluster, 
> because we use different HDFS between yarn cluster and hbase cluster. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to