[ 
https://issues.apache.org/jira/browse/FLINK-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446003#comment-15446003
 ] 

ASF GitHub Bot commented on FLINK-4526:
---------------------------------------

GitHub user mxm opened a pull request:

    https://github.com/apache/flink/pull/2437

    [FLINK-4526][yarn] remove redundant proxy messages

    Merging this with #2423 with #2419.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mxm/flink FLINK-4526

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2437.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 #2437
    
----
commit 6bd2b60670fd5c9b15f8695b8dfaa236fe39e5b4
Author: Maximilian Michels <[email protected]>
Date:   2016-08-30T08:46:22Z

    [FLINK-4526][yarn] remove redundant proxy messages

----


> 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)

Reply via email to