| commit | 4e4e568faa3c3d625433b17bb4d15e0cd7897d7a | [log] [tgz] |
|---|---|---|
| author | Julia Wang <jwang98052@yahoo.com> | Wed Nov 16 11:29:05 2016 -0800 |
| committer | Sergiy Matusevych <motus@apache.org> | Thu Nov 17 17:59:21 2016 -0800 |
| tree | 4b8d9a574773031d285991090e7f35d129c949bf | |
| parent | 4392ab83badf077133bdaeabaaa7168f6588852b [diff] |
[REEF-1669]Removing YarnClient from YarnContainerManager Currently we have both YarnClient and resourceManager (AMRMClientAsync) in YarnContainerManager. We call init() and start() for both of them. But inside driver, we are not able to get correct YarnConfiguration for YarnClient, that makes yarnClient.getNodeReports() fail to connect to RM. In YarnContainerManager, we already have onNodesUpdated() which gives the list of the NodeReports on the fly. yarnClient.getNodeReports() was called at beginning and it only gives a static list. So looks like we don't need to call it anyway. Based on RM folks, REEF should not use YarnClient at driver side. This PR is to remove YarnClient from YarnContainerManager. It also added some logs for environment variables with a lower log level or debug. JIRA: [REEF-1669](https://issues.apache.org/jira/browse/REEF-1669) This closes #1182
Apache REEF™ (Retainable Evaluator Execution Framework) is a library for developing portable applications for cluster resource managers such as Apache Hadoop YARN or Apache Mesos. For example, Microsoft Azure Stream Analytics is built on REEF and Hadoop.
Detailed information on REEF can be found in the following places:
The developer mailing list is the best way to reach REEF‘s developers when the above aren’t sufficient.
| Component | OS | Status |
|---|---|---|
| REEF Java | Ubuntu |  |
| REEF.NET | Windows |
| Java | .NET | |
|---|---|---|
| Build & run unit tests | java\BUILD.md | cs\BUILD.md |
