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

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

GitHub user sachingoel0101 opened a pull request:

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

    [FLINK-2399] Version checks for Job Manager and Task Manager

    Both Job Manager and Task Manager now communicate their respective version 
IDs to each other as part of registration messages.
    Version ID is accessed by the information Maven adds in the manifest. 
However, for enabling the tests to run in IDE[is this necessary?], where the 
version number is null, added a special provision to set the version ID to "", 
when it is null.

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

    $ git pull https://github.com/sachingoel0101/flink FLINK-2399

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

    https://github.com/apache/flink/pull/944.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 #944
    
----
commit b9d517fc26b7bc53ada215b253a3086e744781df
Author: Sachin Goel <[email protected]>
Date:   2015-07-24T15:41:34Z

    Added version checks for Job Manager and Task Manager

----


> Fail when actor versions don't match
> ------------------------------------
>
>                 Key: FLINK-2399
>                 URL: https://issues.apache.org/jira/browse/FLINK-2399
>             Project: Flink
>          Issue Type: Improvement
>          Components: JobManager, TaskManager
>    Affects Versions: 0.9, master
>            Reporter: Ufuk Celebi
>            Priority: Minor
>             Fix For: 0.10
>
>
> Problem: there can be subtle errors when actors from different Flink versions 
> communicate with each other, for example when an old client (e.g. Flink 0.9) 
> communicates with a new JobManager (e.g. Flink 0.10-SNAPSHOT).
> We can check that the versions match on first communication between the 
> actors and fail if they don't match.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to