GitHub user rmetzger opened a pull request:
https://github.com/apache/incubator-flink/pull/86
Improved Error Handling and Usability of the Flink YARN Client
This pull request is addressing the following issues:
* [FLINK-995] TaskManagers are called TaskTracker in NepheleMiniCluster
* [FLINK-968] Add a yarn session parameter for the number of task slots per
task manager
* Users can now set any configuration value using `-D` flags.
* I added a RPC service between the YARN Client and the ApplicationMaster
for better error reporting (and also status information to the user)
* The log view in the webinterface can now handle multiple log directories
(can happen with yarn)
* The webinterface shows the number of slots in the cluster
* Some renamings in the web interface (Apache Flink instead of Flink).
* I also fixed a really annoying bug in the RPC service (it swallowed
basically all exceptions during deserialization of objects send over RPC).
* I've updated the documentation of the YARN client.
The changes have been tested on Amazon EMR and the 25 nodes cluster @ TUB.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rmetzger/incubator-flink
improve_yarn_after_rename_rebased
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-flink/pull/86.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 #86
----
commit d9504290e508ff257bb530b478123dd74541353d
Author: Robert Metzger <[email protected]>
Date: 2014-06-16T15:56:59Z
[YARN] properly set diagnostics messages on failures
commit 59c7a93bc62b2b9fb8d3bd6d8749eaa11c72d1e2
Author: Robert Metzger <[email protected]>
Date: 2014-07-17T08:55:30Z
[FLINK-968] Add slot parameter to YARN client
----
---
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.
---
