+1 for the change(non-binding).
IMO, we should create MapReduce API section and MapredAppMasterRest.apt.vm should be also moved into the section.

Created MapReduce API section and moved MapRedAppMasterRest into hadoop-mapreduce-client-core and HistoryServerRest into hadoop-mapreduce-client-fs.

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12642614/YARN-1999.1.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+0 tests included. The patch appears to be a documentation patch that doesn't require tests.

+1 javac. The applied patch does not increase the total number of javac compiler warnings.

+1 javadoc. There were no new javadoc warning messages.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

+1 release audit. The applied patch does not increase the total number of release audit warnings.

+1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.

+1 contrib tests. The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/3663//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3663//console

This message is automatically generated.

I'm also +1 (non-binding) for the change, and thanks Tsuyoshi Ozawa for taking this issue.
Here are three comments:

• HistoryServerRest.apt.vm looks deleted. You should git add the file and then create a patch.
• Please remove the dead links from YARN REST APIs section in site.xml.
• When moving HistoryServerRest.apt.vm to MapReduce REST APIs section, it would be better to change the sentence

  -  The history server REST API's allow the user to get status on finished applications. Currently it only supports MapReduce and provides information on finished jobs.
  

  like

  The history server REST API's allow the user to get status on finished MapReduce jobs.
  

  because the document itself is now MapReduce-specific.

+1 for reorganizing the web pages. For clarity, maybe it's better to say "Job History Server" instead?

Move the ticket to MR

or "MR History Server" as the section header.

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12642614/YARN-1999.1.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+0 tests included. The patch appears to be a documentation patch that doesn't require tests.

+1 javac. The applied patch does not increase the total number of javac compiler warnings.

+1 javadoc. There were no new javadoc warning messages.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

+1 release audit. The applied patch does not increase the total number of release audit warnings.

+1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.

+1 contrib tests. The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4575//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4575//console

This message is automatically generated.

Thanks for your review, Akira and Zhijie. Updated a patch as follows:

• Changed the section name from "History Server" to "MR History Server"
• Removed dead links from YARN REST APIs' section
• Updated a sentence Akira pointed out
• Moved HistoryServerRest.apt.vm correctly

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12643047/MAPREDUCE-5874.2.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+0 tests included. The patch appears to be a documentation patch that doesn't require tests.

+1 javac. The applied patch does not increase the total number of javac compiler warnings.

+1 javadoc. There were no new javadoc warning messages.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

+1 release audit. The applied patch does not increase the total number of release audit warnings.

+1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs.

+1 contrib tests. The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4576//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4576//console

This message is automatically generated.

Thanks Tsuyoshi Ozawa for updating the patch.
Would you remove the "Go Back" links in the both documents in addition? Since index.html does not exist in the both MapReduce projects, the links become dead.

  \[ {{{./index.html}Go Back}} \]

I'm +1 (non-binding) after that is addressed.

Thanks for your suggestion, Akira. Removed a link to top page from both docs.

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12644468/MAPREDUCE-5874.3.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+0 tests included. The patch appears to be a documentation patch that doesn't require tests.

+1 javac. The applied patch does not increase the total number of javac compiler warnings.

+1 javadoc. There were no new javadoc warning messages.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

+1 release audit. The applied patch does not increase the total number of release audit warnings.

+1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs.

+1 contrib tests. The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4598//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4598//console

This message is automatically generated.

+1 (non-binding)

Were you able to run mvn site:stage ? Mine failed with this error

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on project hadoop-main: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.3:stage failed: A required class was missing while executing org.apache.maven.plugins:maven-site-plugin:3.3:stage: org/apache/commons/lang/StringUtils

Before running "mvn site:stage", it is needed to run "mvn site".
I can run the following command successfully:

$ mvn site; mvn site:stage -DstagingDirectory=/path/to/dir/

I did run mvn site prior to staging. The problem was that I was using maven 3.1.1. Switching to maven 3.2.1 fixed the issue.

I'm +1 on this change. I will commit it shortly. Thanks a lot Tsyoshi and Akira!

I've committed to trunk and branch-2