From 7dbdb7560db66022654c32ffe5d4b238e91aa45b Mon Sep 17 00:00:00 2001 From: Akira Ajisaka Date: Wed, 26 Sep 2018 09:42:53 +0900 Subject: [PATCH] YARN-8752. yarn-registry.md has wrong word ong-lived, it should be long-lived. Contributed by leiqiang. (cherry picked from commit 94b5c54e8af51d178474d2f0eb5505366750ecf4) --- .../src/site/markdown/registry/yarn-registry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/registry/yarn-registry.md b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/registry/yarn-registry.md index 4973862ba82..650682fd8b9 100644 --- a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/registry/yarn-registry.md +++ b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/registry/yarn-registry.md @@ -85,7 +85,7 @@ container ID. ## The binding problem Hadoop YARN allows applications to run on the Hadoop cluster. Some of these are batch jobs or queries that can managed via YARN’s existing API using its -application ID. In addition YARN can deploy ong-lived services instances such a +application ID. In addition YARN can deploy long-lived services instances such a pool of Apache Tomcat web servers or an Apache HBase cluster. YARN will deploy them across the cluster depending on the individual each component requirements and server availability. These service instances need to be discovered by