hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3873) DistCp should have an option for limiting the number of files/bytes being copied
Date Wed, 30 Jul 2008 21:15:31 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618510#action_12618510
] 

Doug Cutting commented on HADOOP-3873:
--------------------------------------

This sounds rather ad-hoc.  What is the use case?

In most cases, the total size to be copied can be determined up front, before the copying
begins, no?

What might be better is a mechanism to stop a DistCp job.  E.g., one could provide a "stop"
file name.  When this is non-null, copying will stop as soon as the named file exists.  Might
that meet the need here?

> DistCp should have an option for limiting the number of files/bytes being copied
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-3873
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3873
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: tools/distcp
>            Reporter: Tsz Wo (Nicholas), SZE
>
> A single DistCp command may potentially copies a huge number of files/bytes.  In such
case, DistCp will run a long time and there is no way stop it nicely.  It would be good if
DistCp have an option to limit the number of files/bytes being copied.  Once the limit is
reached, DistCp will terminate and return success.  All files copied are guaranteed to be
good and there is no partially copied file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message