hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From oz...@apache.org
Subject hadoop git commit: YARN-3805. Update the documentation of Disk Checker based on YARN-90. Contributed by Masatake Iwasaki.
Date Thu, 16 Jul 2015 08:53:27 GMT
Repository: hadoop
Updated Branches:
  refs/heads/branch-2 90c5bf060 -> e97a14ae6


YARN-3805. Update the documentation of Disk Checker based on YARN-90. Contributed by Masatake
Iwasaki.

(cherry picked from commit 1ba2986dee4bbb64d67ada005f8f132e69575274)


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

Branch: refs/heads/branch-2
Commit: e97a14ae6f46ae401d133abceac403647fcdf46b
Parents: 90c5bf0
Author: Tsuyoshi Ozawa <ozawa@apache.org>
Authored: Thu Jul 16 17:52:38 2015 +0900
Committer: Tsuyoshi Ozawa <ozawa@apache.org>
Committed: Thu Jul 16 17:52:58 2015 +0900

----------------------------------------------------------------------
 hadoop-yarn-project/CHANGES.txt                              | 3 +++
 .../hadoop-yarn-site/src/site/markdown/NodeManager.md        | 8 ++++++--
 2 files changed, 9 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hadoop/blob/e97a14ae/hadoop-yarn-project/CHANGES.txt
----------------------------------------------------------------------
diff --git a/hadoop-yarn-project/CHANGES.txt b/hadoop-yarn-project/CHANGES.txt
index 933d0f1..a870ca5 100644
--- a/hadoop-yarn-project/CHANGES.txt
+++ b/hadoop-yarn-project/CHANGES.txt
@@ -586,6 +586,9 @@ Release 2.8.0 - UNRELEASED
     YARN-3174. Consolidate the NodeManager and NodeManagerRestart documentation 
     into one. (Masatake Iwasaki via ozawa)
 
+    YARN-3805. Update the documentation of Disk Checker based on YARN-90.
+    (Masatake Iwasaki via ozawa)
+
 Release 2.7.2 - UNRELEASED
 
   INCOMPATIBLE CHANGES

http://git-wip-us.apache.org/repos/asf/hadoop/blob/e97a14ae/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/NodeManager.md
----------------------------------------------------------------------
diff --git a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/NodeManager.md
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/NodeManager.md
index 69e99a7..4724ea6 100644
--- a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/NodeManager.md
+++ b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/NodeManager.md
@@ -36,7 +36,9 @@ The NodeManager runs services to determine the health of the node it is
executin
 
 ###Disk Checker
 
-  The disk checker checks the state of the disks that the NodeManager is configured to use(local-dirs
and log-dirs, configured using yarn.nodemanager.local-dirs and yarn.nodemanager.log-dirs respectively).
The checks include permissions and free disk space. It also checks that the filesystem isn't
in a read-only state. The checks are run at 2 minute intervals by default but can be configured
to run as often as the user desires. If a disk fails the check, the NodeManager stops using
that particular disk but still reports the node status as healthy. However if a number of
disks fail the check(the number can be configured, as explained below), then the node is reported
as unhealthy to the ResourceManager and new containers will not be assigned to the node. In
addition, once a disk is marked as unhealthy, the NodeManager stops checking it to see if
it has recovered(e.g. disk became full and was then cleaned up). The only way for the NodeManager
to use that disk to restart the software o
 n the node. The following configuration parameters can be used to modify the disk checks:
+  The disk checker checks the state of the disks that the NodeManager is configured to use(local-dirs
and log-dirs, configured using yarn.nodemanager.local-dirs and yarn.nodemanager.log-dirs respectively).
The checks include permissions and free disk space. It also checks that the filesystem isn't
in a read-only state. The checks are run at 2 minute intervals by default but can be configured
to run as often as the user desires. If a disk fails the check, the NodeManager stops using
that particular disk but still reports the node status as healthy. However if a number of
disks fail the check(the number can be configured, as explained below), then the node is reported
as unhealthy to the ResourceManager and new containers will not be assigned to the node.
+
+The following configuration parameters can be used to modify the disk checks:
 
 | Configuration Name | Allowed Values | Description |
 |:---- |:---- |:---- |
@@ -48,7 +50,9 @@ The NodeManager runs services to determine the health of the node it is
executin
 
 ###External Health Script
 
-  Users may specify their own health checker script that will be invoked by the health checker
service. Users may specify a timeout as well as options to be passed to the script. If the
script exits with a non-zero exit code, times out or results in an exception being thrown,
the node is marked as unhealthy. Please note that if the script cannot be executed due to
permissions or an incorrect path, etc, then it counts as a failure and the node will be reported
as unhealthy. Please note that speifying a health check script is not mandatory. If no script
is specified, only the disk checker status will be used to determine the health of the node.
The following configuration parameters can be used to set the health script:
+Users may specify their own health checker script that will be invoked by the health checker
service. Users may specify a timeout as well as options to be passed to the script. If the
script exits with a non-zero exit code, times out or results in an exception being thrown,
the node is marked as unhealthy. Please note that if the script cannot be executed due to
permissions or an incorrect path, etc, then it counts as a failure and the node will be reported
as unhealthy. Please note that speifying a health check script is not mandatory. If no script
is specified, only the disk checker status will be used to determine the health of the node.
+
+The following configuration parameters can be used to set the health script:
 
 | Configuration Name | Allowed Values | Description |
 |:---- |:---- |:---- |


Mime
View raw message