hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aajis...@apache.org
Subject hadoop git commit: YARN-6809. Fix typo in ResourceManagerHA.md. Contributed by Yeliang Cang.
Date Wed, 12 Jul 2017 10:39:40 GMT
Repository: hadoop
Updated Branches:
  refs/heads/branch-2.8 d1fb4948d -> ebb66d203

YARN-6809. Fix typo in ResourceManagerHA.md. Contributed by Yeliang Cang.

(cherry picked from commit b628d0da5196faa5abf4c95dc7e1bb4eb67f6707)
(cherry picked from commit 3419381e988b489d4fde677f2ab191a955724371)

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

Branch: refs/heads/branch-2.8
Commit: ebb66d203831f49ee004ddf91c43f4611b53af07
Parents: d1fb494
Author: Akira Ajisaka <aajisaka@apache.org>
Authored: Wed Jul 12 19:38:32 2017 +0900
Committer: Akira Ajisaka <aajisaka@apache.org>
Committed: Wed Jul 12 19:39:29 2017 +0900

 .../hadoop-yarn-site/src/site/markdown/ResourceManagerHA.md        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/ResourceManagerHA.md
index 49669a1..e3115a1 100644
--- a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/ResourceManagerHA.md
+++ b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/ResourceManagerHA.md
@@ -51,7 +51,7 @@ The RMs have an option to embed the Zookeeper-based ActiveStandbyElector
to deci
 When there are multiple RMs, the configuration (yarn-site.xml) used by clients and nodes
is expected to list all the RMs. Clients, ApplicationMasters (AMs) and NodeManagers (NMs)
try connecting to the RMs in a round-robin fashion until they hit the Active RM. If the Active
goes down, they resume the round-robin polling until they hit the "new" Active. This default
retry logic is implemented as `org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider`.
You can override the logic by implementing `org.apache.hadoop.yarn.client.RMFailoverProxyProvider`
and setting the value of `yarn.client.failover-proxy-provider` to the class name.
-### Recovering prevous active-RM's state
+### Recovering previous active-RM's state
 With the [ResourceManger Restart](./ResourceManagerRestart.html) enabled, the RM being promoted
to an active state loads the RM internal state and continues to operate from where the previous
active left off as much as possible depending on the RM restart feature. A new attempt is
spawned for each managed application previously submitted to the RM. Applications can checkpoint
periodically to avoid losing any work. The state-store must be visible from the both of Active/Standby
RMs. Currently, there are two RMStateStore implementations for persistence - FileSystemRMStateStore
and ZKRMStateStore. The `ZKRMStateStore` implicitly allows write access to a single RM at
any point in time, and hence is the recommended store to use in an HA cluster. When using
the ZKRMStateStore, there is no need for a separate fencing mechanism to address a potential
split-brain situation where multiple RMs can potentially assume the Active role. When using
the ZKRMStateStore, it is advisable to NOT set the
  "`zookeeper.DigestAuthenticationProvider.superDigest`" property on the Zookeeper cluster
to ensure that the zookeeper admin does not have access to YARN application/user credential

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

View raw message