[
https://issues.apache.org/jira/browse/FLINK-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643192#comment-14643192
]
ASF GitHub Bot commented on FLINK-2399:
---------------------------------------
GitHub user sachingoel0101 opened a pull request:
https://github.com/apache/flink/pull/945
[FLINK-2399] Version checks for Job Manager and Task Manager
[Reopening #944. The travis build failed somehow. ]
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.
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/945.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 #945
----
commit 6de306bccb4687177c49d9baa6e40940db7a8ff9
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)
