You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/08/29 16:22:20 UTC
[jira] [Closed] (FLINK-4526) ApplicationClient: remove redundant
proxy messages
[ https://issues.apache.org/jira/browse/FLINK-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maximilian Michels closed FLINK-4526.
-------------------------------------
Resolution: Fixed
master: 31c88a564a8eda263aedada0da671357d1a6f524
release-1.1: f7ec1efb32c277a0d51479cca4450edb324a3d58
> ApplicationClient: remove redundant proxy messages
> --------------------------------------------------
>
> Key: FLINK-4526
> URL: https://issues.apache.org/jira/browse/FLINK-4526
> Project: Flink
> Issue Type: Bug
> Components: YARN Client
> Affects Versions: 1.2.0, 1.1.1
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Fix For: 1.2.0, 1.1.2
>
>
> {{GetClusterStatus}} and {{ShutdownClusterAfterJob}} don't have to be proxied through the ApplicationClient's messages {{LocalGetyarnClusterStatus}} and {{LocalStopAMAfterJob}}. These messages can be directly handled by the client. The implementations are also faulty in the sense that they don't reply to the client in case the leader is not available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)