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

Hudson commented on HBASE-20579:
--------------------------------

Results for branch branch-2
        [build #817 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/817/]: 
(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/branch-2/817//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/branch-2/817//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/branch-2/817//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> Improve snapshot manifest copy in ExportSnapshot
> ------------------------------------------------
>
>                 Key: HBASE-20579
>                 URL: https://issues.apache.org/jira/browse/HBASE-20579
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce
>    Affects Versions: 1.4.0, 1.5.0, 2.0.0
>            Reporter: Jingyun Tian
>            Assignee: Jingyun Tian
>            Priority: Minor
>             Fix For: 3.0.0, 2.1.0
>
>         Attachments: HBASE-20579.branch-2.addendum.patch, 
> HBASE-20579.master.001.patch, HBASE-20579.master.002.patch
>
>
> ExportSnapshot need to copy snapshot manifest to destination cluster first, 
> then setOwner and setPermission for those paths. But it's done with one 
> thread, which lead to a long time to submit the job if your snapshot is big. 
> I tried to make them processing in parallel, which can reduce the total time 
> of submitting dramatically. 



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

Reply via email to