[2/2] hadoop git commit: YARN-8133. Doc link broken for yarn-service from overview page. (Rohith Sharma K S via wangda)

2018-04-10 Thread wangda 
YARN-8133. Doc link broken for yarn-service from overview page. (Rohith Sharma 
K S via wangda)

Change-Id: Iacf9a004585dd59e1c0cd8f8c618a38f047cc0fe
(cherry picked from commit d919eb6efa1072517017c75fb323e391f4418dc8)


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

Branch: refs/heads/branch-3.1
Commit: 53abef4e30cdfa5cfe9fd3eccf06e26da8b56dd2
Parents: f5dc7d1
Author: Wangda Tan 
Authored: Tue Apr 10 17:33:15 2018 -0700
Committer: Wangda Tan 
Committed: Tue Apr 10 17:38:37 2018 -0700

--
 .../src/site/markdown/yarn-service/Concepts.md|  6 +++---
 .../src/site/markdown/yarn-service/Overview.md| 14 +++---
 .../src/site/markdown/yarn-service/QuickStart.md  | 12 ++--
 .../src/site/markdown/yarn-service/RegistryDNS.md |  4 ++--
 .../site/markdown/yarn-service/ServiceDiscovery.md|  4 ++--
 5 files changed, 20 insertions(+), 20 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/hadoop/blob/53abef4e/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Concepts.md
--
diff --git 
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Concepts.md
 
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Concepts.md
index e567d03..5c77f17 100644
--- 
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Concepts.md
+++ 
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Concepts.md
@@ -29,7 +29,7 @@ affinity and anti-affinity scheduling, log aggregation for 
services, automatical
 A restful API server is developed to allow users to deploy/manage their 
services on YARN via a simple JSON spec. This avoids users
 from dealing with the low-level APIs, writing complex code to bring their 
services onto YARN. The REST layer acts as a unified REST based entry for
 creation and lifecycle management of YARN services. Services here can range 
from simple single-component apps to the most complex, 
-multi-component applications needing special orchestration needs. Please refer 
to this [API doc](YarnServiceAPI.md) for detailed API documentations.
+multi-component applications needing special orchestration needs. Please refer 
to this [API doc](YarnServiceAPI.html) for detailed API documentations.
 
 The API-server is stateless, which means users can simply spin up multiple 
instances, and have a load balancer fronting them to 
 support HA, distribute the load etc.
@@ -37,10 +37,10 @@ support HA, distribute the load etc.
 ### Service Discovery
 A DNS server is implemented to enable discovering services on YARN via the 
standard mechanism: DNS lookup.
 
-The framework posts container information such as hostname and ip into the 
[YARN service registry](../registry/index.md). And the DNS server essentially 
exposes the
+The framework posts container information such as hostname and ip into the 
[YARN service registry](../registry/index.html). And the DNS server essentially 
exposes the
 information in YARN service registry by translating them into DNS records such 
as A record and SRV record.
 Clients can then discover the IPs of containers via standard DNS lookup.
 
 The previous read mechanisms of YARN Service Registry were limited to a 
registry specific (java) API and a REST interface and are difficult
-to wireup existing clients and services. The DNS based service discovery 
eliminates this gap. Please refer to this [Service Discovery 
doc](ServiceDiscovery.md)
+to wireup existing clients and services. The DNS based service discovery 
eliminates this gap. Please refer to this [Service Discovery 
doc](ServiceDiscovery.html)
 for more details.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/hadoop/blob/53abef4e/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Overview.md
--
diff --git 
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Overview.md
 
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Overview.md
index 72c2d3e..8e2bf9a 100644
--- 
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Overview.md
+++ 
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Overview.md
@@ -46,16 +46,16 @@ The benefits of combining these workloads are two-fold:
 
 *`This feature is in alpha state`* and so APIs, command lines are subject to 
change. We will continue

[2/2] hadoop git commit: YARN-8133. Doc link broken for yarn-service from overview page. (Rohith Sharma K S via wangda)

2018-04-10 Thread wangda 
YARN-8133. Doc link broken for yarn-service from overview page. (Rohith Sharma 
K S via wangda)

Change-Id: Iacf9a004585dd59e1c0cd8f8c618a38f047cc0fe


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

Branch: refs/heads/trunk
Commit: d919eb6efa1072517017c75fb323e391f4418dc8
Parents: 2bf9cc2
Author: Wangda Tan 
Authored: Tue Apr 10 17:33:15 2018 -0700
Committer: Wangda Tan 
Committed: Tue Apr 10 17:33:15 2018 -0700

--
 .../src/site/markdown/yarn-service/Concepts.md|  6 +++---
 .../src/site/markdown/yarn-service/Overview.md| 14 +++---
 .../src/site/markdown/yarn-service/QuickStart.md  | 12 ++--
 .../src/site/markdown/yarn-service/RegistryDNS.md |  4 ++--
 .../site/markdown/yarn-service/ServiceDiscovery.md|  4 ++--
 5 files changed, 20 insertions(+), 20 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/hadoop/blob/d919eb6e/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Concepts.md
--
diff --git 
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Concepts.md
 
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Concepts.md
index e567d03..5c77f17 100644
--- 
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Concepts.md
+++ 
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Concepts.md
@@ -29,7 +29,7 @@ affinity and anti-affinity scheduling, log aggregation for 
services, automatical
 A restful API server is developed to allow users to deploy/manage their 
services on YARN via a simple JSON spec. This avoids users
 from dealing with the low-level APIs, writing complex code to bring their 
services onto YARN. The REST layer acts as a unified REST based entry for
 creation and lifecycle management of YARN services. Services here can range 
from simple single-component apps to the most complex, 
-multi-component applications needing special orchestration needs. Please refer 
to this [API doc](YarnServiceAPI.md) for detailed API documentations.
+multi-component applications needing special orchestration needs. Please refer 
to this [API doc](YarnServiceAPI.html) for detailed API documentations.
 
 The API-server is stateless, which means users can simply spin up multiple 
instances, and have a load balancer fronting them to 
 support HA, distribute the load etc.
@@ -37,10 +37,10 @@ support HA, distribute the load etc.
 ### Service Discovery
 A DNS server is implemented to enable discovering services on YARN via the 
standard mechanism: DNS lookup.
 
-The framework posts container information such as hostname and ip into the 
[YARN service registry](../registry/index.md). And the DNS server essentially 
exposes the
+The framework posts container information such as hostname and ip into the 
[YARN service registry](../registry/index.html). And the DNS server essentially 
exposes the
 information in YARN service registry by translating them into DNS records such 
as A record and SRV record.
 Clients can then discover the IPs of containers via standard DNS lookup.
 
 The previous read mechanisms of YARN Service Registry were limited to a 
registry specific (java) API and a REST interface and are difficult
-to wireup existing clients and services. The DNS based service discovery 
eliminates this gap. Please refer to this [Service Discovery 
doc](ServiceDiscovery.md)
+to wireup existing clients and services. The DNS based service discovery 
eliminates this gap. Please refer to this [Service Discovery 
doc](ServiceDiscovery.html)
 for more details.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/hadoop/blob/d919eb6e/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Overview.md
--
diff --git 
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Overview.md
 
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Overview.md
index 72c2d3e..8e2bf9a 100644
--- 
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Overview.md
+++ 
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/Overview.md
@@ -46,16 +46,16 @@ The benefits of combining these workloads are two-fold:
 
 *`This feature is in alpha state`* and so APIs, command lines are subject to 
change. We will continue to update the documents over time.
 
-[QuickStart](QuickStart.md) shows a