[
https://issues.apache.org/jira/browse/FLINK-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354833#comment-15354833
]
ASF GitHub Bot commented on FLINK-4127:
---------------------------------------
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/2177#discussion_r68908671
--- Diff: docs/setup/config.md ---
@@ -107,12 +109,20 @@ Please make sure to set the maximum ticket life span
high long running jobs. The
If you are on YARN, then it is sufficient to authenticate the client with
Kerberos. On a Flink standalone cluster you need to ensure that, initially, all
nodes are authenticated with Kerberos using the `kinit` tool.
+### Resource Manager
+
+- `resourcemanager.rpc.port`: The config parameter defining the network
port to connect to for communication with the resource manager.
--- End diff --
No, it doesn't. It is currently not in use (except for testing code). In
Yarn, the port of the application master is always the port of the job manager
because the two run in the same actor system.
> Clean up configuration and check breaking API changes
> -----------------------------------------------------
>
> Key: FLINK-4127
> URL: https://issues.apache.org/jira/browse/FLINK-4127
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Reporter: Robert Metzger
> Assignee: Robert Metzger
> Fix For: 1.1.0
>
> Attachments: flink-core.html, flink-java.html, flink-scala.html,
> flink-streaming-java.html, flink-streaming-scala.html
>
>
> For the upcoming 1.1. release, I'll check if there are any breaking API
> changes and if the documentation is up tp date with the configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
