tree 4b8d9a574773031d285991090e7f35d129c949bf
parent 4392ab83badf077133bdaeabaaa7168f6588852b
author Julia Wang <jwang98052@yahoo.com> 1479324545 -0800
committer Sergiy Matusevych <motus@apache.org> 1479434361 -0800

[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