Eric Badger 87816e8a51 YARN-10363. TestRMAdminCLI.testHelp is failing in branch-2.10. Contributed by 4 anni fa
..
bin 246086984e YARN-7773. YARN Federation used Mysql as state store throw exception, Unknown column 'homeSubCluster' in 'field list'. Contributed by Yiran Wu. 6 anni fa
conf 1978317068 YARN-2255. YARN Audit logging not added to log4j.properties. Contributed by Aihua Xu. 5 anni fa
dev-support 4d274f60bc Make upstream aware of 2.10.0 release 5 anni fa
hadoop-yarn-api 8d8366166e YARN-1529: Add Localization overhead metrics to NM. Contributed by Jim_Brennan. 4 anni fa
hadoop-yarn-applications 4592af898b HADOOP-17100. Replace Guava Supplier with Java8+ Supplier in Hadoop. Contributed by Ahmed Hussein. 4 anni fa
hadoop-yarn-client 87816e8a51 YARN-10363. TestRMAdminCLI.testHelp is failing in branch-2.10. Contributed by 4 anni fa
hadoop-yarn-common b7b9bd32db HADOOP-17099. Replace Guava Predicate with Java8+ Predicate 4 anni fa
hadoop-yarn-registry ec6d2a8402 Preparing for 3.1.5 development 5 anni fa
hadoop-yarn-server 8d8366166e YARN-1529: Add Localization overhead metrics to NM. Contributed by Jim_Brennan. 4 anni fa
hadoop-yarn-site ec6d2a8402 Preparing for 3.1.5 development 5 anni fa
hadoop-yarn-ui ec6d2a8402 Preparing for 3.1.5 development 5 anni fa
shellprofile.d 730bc746f9 HADOOP-12930. Dynamic subcommands for hadoop shell scripts (aw) 9 anni fa
README c9b525bd94 YARN-6943. Update Yarn to YARN in documentation. Contributed by Chetna Chaudhari. 7 anni fa
pom.xml ec6d2a8402 Preparing for 3.1.5 development 5 anni fa

README

YARN (YET ANOTHER RESOURCE NEGOTIATOR or YARN Application Resource Negotiator)
------------------------------------------------------------------------------

Requirements
-------------
Java: JDK 1.6
Maven: Maven 3

Setup
-----
Install protobuf 2.5.0 (Download from http://code.google.com/p/protobuf/downloads/list)
- install the protoc executable (configure, make, make install)
- install the maven artifact (cd java; mvn install)


Quick Maven Tips
----------------
clean workspace: mvn clean
compile and test: mvn install
skip tests: mvn install -DskipTests
skip test execution but compile: mvn install -Dmaven.test.skip.exec=true
clean and test: mvn clean install
run selected test after compile: mvn test -Dtest=TestClassName (combined: mvn clean install -Dtest=TestClassName)
create runnable binaries after install: mvn assembly:assembly -Pnative (combined: mvn clean install assembly:assembly -Pnative)

Eclipse Projects
----------------
http://maven.apache.org/guides/mini/guide-ide-eclipse.html

1. Generate .project and .classpath files in all maven modules
mvn eclipse:eclipse
CAUTION: If the project structure has changed from your previous workspace, clean up all .project and .classpath files recursively. Then run:
mvn eclipse:eclipse

2. Import the projects in eclipse.

3. Set the environment variable M2_REPO to point to your .m2/repository location.

NetBeans Projects
-----------------

NetBeans has builtin support of maven projects. Just "Open Project..."
and everything is setup automatically. Verified with NetBeans 6.9.1.


Custom Hadoop Dependencies
--------------------------

By default Hadoop dependencies are specified in the top-level pom.xml
properties section. One can override them via -Dhadoop-common.version=...
on the command line. ~/.m2/settings.xml can also be used to specify
these properties in different profiles, which is useful for IDEs.

Modules
-------
YARN consists of multiple modules. The modules are listed below as per the directory structure:

hadoop-yarn-api - YARN's cross platform external interface

hadoop-yarn-common - Utilities which can be used by yarn clients and server

hadoop-yarn-server - Implementation of the hadoop-yarn-api
hadoop-yarn-server-common - APIs shared between resourcemanager and nodemanager
hadoop-yarn-server-nodemanager (TaskTracker replacement)
hadoop-yarn-server-resourcemanager (JobTracker replacement)

Utilities for understanding the code
------------------------------------
Almost all of the yarn components as well as the mapreduce framework use
state-machines for all the data objects. To understand those central pieces of
the code, a visual representation of the state-machines helps much. You can first
convert the state-machines into graphviz(.gv) format by
running:
mvn compile -Pvisualize
Then you can use the dot program for generating directed graphs and convert the above
.gv files to images. The graphviz package has the needed dot program and related
utilites.For e.g., to generate png files you can run:
dot -Tpng NodeManager.gv > NodeManager.png