[
https://issues.apache.org/jira/browse/FLINK-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978323#comment-15978323
]
ASF GitHub Bot commented on FLINK-6155:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3596
Good changes!
I think we could actually drop the explicit endpoint name from the
`TaskExecutor` and always let it use a random name (as is the default when no
explicit name is given). That would simplify the code a bit and it should work
since the connection is always established by the `TaskExecutor` towards the
`ResourceManager` and `JobManager`, but never the the other way around.
> Allow to specify endpoint names
> -------------------------------
>
> Key: FLINK-6155
> URL: https://issues.apache.org/jira/browse/FLINK-6155
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination
> Affects Versions: 1.3.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Fix For: 1.3.0
>
>
> In order to make the standalone mode work, we have to be able to assign names
> to the {{RpcEndpoints}}. In the case of the Akka implementation they would
> correspond to the actor names. This information is necessary to look the
> corresponding endpoints up on a remote host because in standalone mode the
> names have to be deterministic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)