GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/flink/pull/3614
[FLINK-6189][YARN]Do not use yarn client config to do sanity check
Now in client, if #slots is greater than then number of
"yarn.nodemanager.resource.cpu-vcores" in yarn client config, the submission
will be rejected.
It makes no sense as the actual vcores of node manager is decided in
cluster side, but not in client side. If we don't set the config or don't set
the right value of it(indeed this config is not a mandatory), it should not
affect flink submission.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/WangTaoTheTonic/flink FLINK-6189
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3614.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3614
----
commit eef3bba405557c6f7c55aee6983bb1bd9ade7501
Author: WangTaoTheTonic <[email protected]>
Date: 2017-03-25T10:00:35Z
Do not use yarn client config to do sanity check
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
