big-data/hadoop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HDFS-9889. Update balancer/mover document about HDFS-6133 feature. Contributed by Yongjun Zhang.

Browse Source
This commit is contained in:
Yongjun Zhang 2016-03-04 13:25:29 -08:00
parent 3e8099a45a
commit 8e08861a14
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSCommands.md
View File

@ -285,6 +285,8 @@ Runs a cluster balancing utility. An administrator can simply press Ctrl-C to st
Note that the `blockpool` policy is more strict than the `datanode` policy. Note that the `blockpool` policy is more strict than the `datanode` policy.
Besides the above command options, a pinning feature is introduced starting from 2.7.0 to prevent certain replicas from getting moved by balancer/mover. This pinning feature is disabled by default, and can be enabled by configuration property "dfs.datanode.block-pinning.enabled". When enabled, this feature only affects blocks that are written to favored nodes specified in the create() call. This feature is useful when we want to maintain the data locality, for applications such as HBase regionserver.
### `cacheadmin` ### `cacheadmin`
Usage: `hdfs cacheadmin -addDirective -path <path> -pool <pool-name> [-force] [-replication <replication>] [-ttl <time-to-live>]` Usage: `hdfs cacheadmin -addDirective -path <path> -pool <pool-name> [-force] [-replication <replication>] [-ttl <time-to-live>]`
@ -445,6 +447,8 @@ Runs the data migration utility. See [Mover](./ArchivalStorage.html#Mover_-_A_Ne
Note that, when both -p and -f options are omitted, the default path is the root directory. Note that, when both -p and -f options are omitted, the default path is the root directory.
In addition, a pinning feature is introduced starting from 2.7.0 to prevent certain replicas from getting moved by balancer/mover. This pinning feature is disabled by default, and can be enabled by configuration property "dfs.datanode.block-pinning.enabled". When enabled, this feature only affects blocks that are written to favored nodes specified in the create() call. This feature is useful when we want to maintain the data locality, for applications such as HBase regionserver.
### `namenode` ### `namenode`
Usage: Usage: