## What is the purpose of the change See. [FLINK-5542](https://issues.apache.org/jira/browse/FLINK-5542)
use YarnCluster vcores setting to do MaxVCore validation instead of using the local yarn conf. ## Brief change log - *Fetch MaxVCore num via yarnClient instead of using the local yarn conf* ## Verifying this change This change is a trivial rework / code cleanup without any test coverage. But I already reproduced the [Error/Exception](http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/1-1-4-on-YARN-vcores-change-td11016.html), after the fix, it's working as expected. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (not documented) [ Full content available at: https://github.com/apache/flink/pull/6775 ] This message was relayed via gitbox.apache.org for [email protected]
