yarn integration in the ozone line
yarn integration in the ozone line
added comment
Integrate Yarn with maven profiles
So the yarn-related projects are only imported if building a stratosphere with yarn (hadoop2).

- Remove the cloudera repository from our main pom: It is considered as bad practice to refer to other dependencies outside of maven central. Out project can now be build completely from maven central.
- pact-hbase now uses a different hbase version (I only changed the minor version). But we can not use the "cdh" version anymore. Since there are no tests for hbase, I can not validate if everything is still working.
(1) Changed memory assignment for TMs in YARN mode. (2) Fixed some minor bugs.
add missing dependency for yarn
some leftovers from the merge
seems like something is happening
properly init log4j
remove DiscoveryService in Job- and TaskManager. Replace with new strategy to determine TM's own address.
add nicer debug messages. Fix testcase
remove sys.err
remove the individual yarn start scripts and merge them to the regular Job- and TaskManager scripts
add option to pact client [ci skip]
Make JobClient an interface, change YarnJobClient to implement this interface. Add the wiring inside pact-client to allow submission to YARN. Missing: proper maven dependencies
merge yarn and yarn-common. add nephele-noyarn project. do some profiles magic
finalized non-yarn package
looks like I have to supply the compiler with a InstanceTypeDescription
Correct constructor for YarnJobClient in nonyarn
add comments to RemoteExecutor, improve argument names