hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vvasu...@apache.org
Subject [11/50] [abbrv] hadoop git commit: HDFS-10639. Fix typos in HDFSDiskbalancer.md. Contributed by Yiqun Lin.
Date Mon, 25 Jul 2016 08:24:59 GMT
HDFS-10639. Fix typos in HDFSDiskbalancer.md. Contributed by Yiqun Lin.


Project: http://git-wip-us.apache.org/repos/asf/hadoop/repo
Commit: http://git-wip-us.apache.org/repos/asf/hadoop/commit/5b4a7087
Tree: http://git-wip-us.apache.org/repos/asf/hadoop/tree/5b4a7087
Diff: http://git-wip-us.apache.org/repos/asf/hadoop/diff/5b4a7087

Branch: refs/heads/YARN-4757
Commit: 5b4a708704b7f6172f087d6cfe43114dfab57f53
Parents: da456ff
Author: Akira Ajisaka <aajisaka@apache.org>
Authored: Fri Jul 15 21:41:57 2016 -0700
Committer: Akira Ajisaka <aajisaka@apache.org>
Committed: Fri Jul 15 21:41:57 2016 -0700

----------------------------------------------------------------------
 .../hadoop-hdfs/src/site/markdown/HDFSDiskbalancer.md     | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hadoop/blob/5b4a7087/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSDiskbalancer.md
----------------------------------------------------------------------
diff --git a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSDiskbalancer.md b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSDiskbalancer.md
index c5f73cd..aea440a 100644
--- a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSDiskbalancer.md
+++ b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSDiskbalancer.md
@@ -28,7 +28,7 @@ Diskbalancer is a command line tool that distributes data evenly on all
disks of
 This tool is different from  [Balancer](./HdfsUserGuide.html#Balancer)  which
 takes care of cluster-wide data balancing. Data can have uneven spread between
 disks on a node due to several reasons. This can happen due to large amount of
-writes and deletes or due to a disk replacement.This tool operates against a given datanode
and moves blocks from one disk to another.
+writes and deletes or due to a disk replacement. This tool operates against a given datanode
and moves blocks from one disk to another.
 
 
 
@@ -38,7 +38,7 @@ Architecture
 Disk Balancer operates by creating a plan and goes on to execute that plan on the datanode.
 A plan is a set of statements that describe how much data should move between two disks.
 A plan is composed of multiple move steps. A move step has source disk, destination
-disk and number of bytes to move.A plan can be executed against an operational data node.
Disk balancer should not
+disk and number of bytes to move. A plan can be executed against an operational data node.
Disk balancer should not
 interfere with other processes since it throttles how much data is copied
 every second. Please note that disk balancer is not enabled by default on a cluster.
 To enable diskbalancer `dfs.disk.balancer.enabled` must be set to `true` in hdfs-site.xml.
@@ -63,8 +63,8 @@ The following sections discusses what commands are supported by disk balancer
 | COMMAND\_OPTION    | Description |
 |:---- |:---- |
 | `-out`| Allows user to control the output location of the plan file.|
-| `-bandwidth`| Since datanode is operational and might be running other jobs, diskbalancer
limits the amount of data moved per second. This parameter allows user to set the maximum
bandwidth to be used. This is not required to be set since diskBalancer will use the deafult
bandwidth if this is not specified.|
-| `-thresholdPercentage`| Since we operate against a snap-shot of datanode, themove operations
have a tolerance percentage to declare success. If user specifies 10% and move operation is
say 20GB in size, if we can move 18GB that operation is considered successful. This is to
accomodate the changes in datanode in real time. This parameter is not needed and a default
is used if not specified.|
+| `-bandwidth`| Since datanode is operational and might be running other jobs, diskbalancer
limits the amount of data moved per second. This parameter allows user to set the maximum
bandwidth to be used. This is not required to be set since diskBalancer will use the default
bandwidth if this is not specified.|
+| `-thresholdPercentage`| Since we operate against a snap-shot of datanode, the move operations
have a tolerance percentage to declare success. If user specifies 10% and move operation is
say 20GB in size, if we can move 18GB that operation is considered successful. This is to
accommodate the changes in datanode in real time. This parameter is not needed and a default
is used if not specified.|
 | `-maxerror` | Max error allows users to specify how many block copy operations must fail
before we abort a move step. Once again, this is not a needed parameter and a system-default
is used if not specified.|
 | `-v`| Verbose mode, specifying this parameter forces the plan command to print out a summary
of the plan on stdout.|
 
@@ -117,4 +117,4 @@ There is a set of diskbalancer settings that can be controlled via hdfs-site.xml
 |`dfs.disk.balancer.enabled`| This parameter controls if diskbalancer is enabled for a cluster.
if this is not enabled, any execute command will be rejected by the datanode.The default value
is false.|
 |`dfs.disk.balancer.max.disk.throughputInMBperSec` | This controls the maximum disk bandwidth
consumed by diskbalancer while copying data. If a value like 10MB is specified then diskbalancer
on the average will only copy 10MB/S. The default value is 10MB/S.|
 |`dfs.disk.balancer.max.disk.errors`| sets the value of maximum number of errors we can ignore
for a specific move between two disks before it is abandoned. For example, if a plan has 3
pair of disks to copy between , and the first disk set encounters more than 5 errors, then
we abandon the first copy and start the second copy in the plan. The default value of max
errors is set to 5.|
-|`dfs.disk.balancer.block.tolerance.percent`| The tolerance percent sepcifies when we have
reached a good enough value for any copy step. For example, if you specify 10% then getting
close to 10% of the target value is good enough.|
+|`dfs.disk.balancer.block.tolerance.percent`| The tolerance percent specifies when we have
reached a good enough value for any copy step. For example, if you specify 10% then getting
close to 10% of the target value is good enough.|


---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-commits-help@hadoop.apache.org


Mime
View raw message