Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7F55E200BAC for ; Wed, 26 Oct 2016 20:30:35 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7DCE2160AEE; Wed, 26 Oct 2016 18:30:35 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C6589160B02 for ; Wed, 26 Oct 2016 20:30:34 +0200 (CEST) Received: (qmail 24942 invoked by uid 500); 26 Oct 2016 18:30:28 -0000 Mailing-List: contact common-commits-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-commits@hadoop.apache.org Received: (qmail 23272 invoked by uid 99); 26 Oct 2016 18:30:27 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Oct 2016 18:30:27 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id D42C2E0B49; Wed, 26 Oct 2016 18:30:27 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: kasha@apache.org To: common-commits@hadoop.apache.org Date: Wed, 26 Oct 2016 18:30:59 -0000 Message-Id: In-Reply-To: <78db06c39b8241a28a5d7156109f6a7a@git.apache.org> References: <78db06c39b8241a28a5d7156109f6a7a@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [33/50] [abbrv] hadoop git commit: Revert "Fix HDFS-11040" archived-at: Wed, 26 Oct 2016 18:30:35 -0000 Revert "Fix HDFS-11040" This reverts commit 54c18157904dc85ce57fc4230a743e171b21fa58. Project: http://git-wip-us.apache.org/repos/asf/hadoop/repo Commit: http://git-wip-us.apache.org/repos/asf/hadoop/commit/3a605730 Tree: http://git-wip-us.apache.org/repos/asf/hadoop/tree/3a605730 Diff: http://git-wip-us.apache.org/repos/asf/hadoop/diff/3a605730 Branch: refs/heads/YARN-4752 Commit: 3a605730390033453b38ce7f41a007ed03900928 Parents: 54c1815 Author: Yongjun Zhang Authored: Tue Oct 25 12:25:02 2016 -0700 Committer: Yongjun Zhang Committed: Tue Oct 25 12:25:02 2016 -0700 ---------------------------------------------------------------------- hadoop-tools/hadoop-distcp/src/site/markdown/DistCp.md.vm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/hadoop/blob/3a605730/hadoop-tools/hadoop-distcp/src/site/markdown/DistCp.md.vm ---------------------------------------------------------------------- diff --git a/hadoop-tools/hadoop-distcp/src/site/markdown/DistCp.md.vm b/hadoop-tools/hadoop-distcp/src/site/markdown/DistCp.md.vm index 40c6b04..e9cfdc7 100644 --- a/hadoop-tools/hadoop-distcp/src/site/markdown/DistCp.md.vm +++ b/hadoop-tools/hadoop-distcp/src/site/markdown/DistCp.md.vm @@ -233,8 +233,7 @@ Flag | Description | Notes `-bandwidth` | Specify bandwidth per map, in MB/second. | Each map will be restricted to consume only the specified bandwidth. This is not always exact. The map throttles back its bandwidth consumption during a copy, such that the **net** bandwidth used tends towards the specified value. `-atomic {-tmp }` | Specify atomic commit, with optional tmp directory. | `-atomic` instructs DistCp to copy the source data to a temporary target location, and then move the temporary target to the final-location atomically. Data will either be available at final target in a complete and consistent form, or not at all. Optionally, `-tmp` may be used to specify the location of the tmp-target. If not specified, a default is chosen. **Note:** tmp_dir must be on the final target cluster. `-async` | Run DistCp asynchronously. Quits as soon as the Hadoop Job is launched. | The Hadoop Job-id is logged, for tracking. -`-diff ` | Use snapshot diff report between given two snapshots to identify the difference between source and target, and apply the diff to the target to make it in sync with source. | This option is valid only with `-update` option and the following conditions should be satisfied.
  1. Both the source and the target FileSystem must be DistributedFileSystem.
  2. Two snapshots `` and `` have been created on the source FS, and `` is older than ``.
  3. The target has the same snapshot ``. No changes have been made on the target since `` was created, thus `` has the same content as the current state of the target. All the files/directories in the target are the same with source's ``.
| -`-rdiff ` | Use snapshot diff report between given two snapshots to identify what has been changed on the target since the snapshot `` was created on the target, and apply the diff reversely to the target, and copy modified files from the source's ``, to make the target the same as ``. | This option is valid only with `-update` option and the following conditions should be satisfied.
  1. Both the source and the target FileSystem must be DistributedFileSystem. The source and the target can be two different clusters/paths, or they can be exactly the same cluster/path. In the latter case, modified files are copied from target's `` to target's current state).
  2. Two snapshots `` and `` have been created on the target FS, and `` is older than ``. No change has been made on target since `` was created on the target.
  3. The sour ce has the same snapshot ``, which has the same content as the `` on the target. All the files/directories in the target's `` are the same with source's ``.
| +`-diff ` | Use snapshot diff report between given two snapshots to identify the difference between source and target. | This option is valid only with `-update` option and the following conditions should be satisfied. 1. Both the source and target FileSystem must be DistributedFileSystem. 2. Two snapshots (e.g., s1 and s2) have been created on the source FS. The diff between these two snapshots will be copied to the target FS. 3. The target has the same snapshot s1. No changes have been made on the target since s1. All the files/directories in the target are the same with source.s1. | `-numListstatusThreads` | Number of threads to use for building file listing | At most 40 threads. `-skipcrccheck` | Whether to skip CRC checks between source and target paths. | --------------------------------------------------------------------- To unsubscribe, e-mail: common-commits-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-commits-help@hadoop.apache.org