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

Hadoop QA commented on HDFS-15022:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  9s{color} 
| {color:red} HDFS-15022 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-15022 |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/28483/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> Add new RPC to transfer data block with external shell script across Datanode
> -----------------------------------------------------------------------------
>
>                 Key: HDFS-15022
>                 URL: https://issues.apache.org/jira/browse/HDFS-15022
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>            Reporter: Yang Yun
>            Assignee: Yang Yun
>            Priority: Minor
>         Attachments: HDFS-15022.patch, HDFS-15022.patch, 
> link_block_across_datanode.pdf
>
>
> Replicating data block is expensive when some Datanodes are down, especially 
> for slow storage. Add a new RPC to replicate block with external shell script 
> across datanode. User can choose more effective way to copy block files.
> In our setup, Archive volume are configured to remote reliable storage. we 
> just add a new link file in new datanode to the remote file when do 
> replication.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to