[
https://issues.apache.org/jira/browse/FLINK-4580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509762#comment-15509762
]
ASF GitHub Bot commented on FLINK-4580:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/2473
Yes agreed. One will always eventually find out about a wrongly connected
rpc endpoint if we introduce a proper error reporting in case of a method
lookup/invocation failure.
> Check that the RpcEndpoint supports the specified RpcGateway
> ------------------------------------------------------------
>
> Key: FLINK-4580
> URL: https://issues.apache.org/jira/browse/FLINK-4580
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination
> Affects Versions: 1.2.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Minor
>
> When calling {{RpcService.connect}} the user specifies the type of the
> {{RpcGateway}}. At the moment, it is not checked whether the {{RpcEndpoint}}
> actually supports the specified {{RpcGateway}}.
> I think it would be good to add a runtime check that the corresponding
> {{RpcEndpoint}} supports the specified {{RpcGateway}}. If not, then we can
> let the connect method fail fast.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
