You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Josh Wills (JIRA)" <ji...@apache.org> on 2019/01/25 02:10:00 UTC

[jira] [Resolved] (CRUNCH-660) FileTargetImpl uses Distcp vs FileUtils.copy

     [ https://issues.apache.org/jira/browse/CRUNCH-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Wills resolved CRUNCH-660.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

Merged!

> FileTargetImpl uses Distcp vs FileUtils.copy
> --------------------------------------------
>
>                 Key: CRUNCH-660
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-660
>             Project: Crunch
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Micah Whitacre
>            Assignee: Josh Wills
>            Priority: Major
>             Fix For: 1.0.0
>
>
> So for handling multiple runtimes I'm not sure there is a way to solve this but documenting as a JIRA regardless.
> If you are running in a multi-cluster environment where you might want to read data from one cluster and then write the output on another cluster (e.g. generating HFiles to be loaded into a separate HBase cluster), the performance of moving files is noticeable.  Specifically due to the fact that the moving of the files happens in the launcher/driver process versus as part of the node execution it seems.[1]
> An efficient option would be to kick off a DistCp instead but that would tie the target directly to a runtime which is not a great approach.  
> [1] - https://github.com/apache/crunch/blob/5609b014378d3460a55ce25522f0c00659872807/crunch-core/src/main/java/org/apache/crunch/io/impl/FileTargetImpl.java#L157



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