[
https://issues.apache.org/jira/browse/HADOOP-8968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484527#comment-13484527
]
Alejandro Abdelnur commented on HADOOP-8968:
--------------------------------------------
@Eli, you are right on buildversion matching and version not and so on. This
was introduced by HADOOP-8209. I think that should be fixed. But it is
different from the issue this JIRA is trying to solve, to allow different
versions of the JT/TT DN/NN to work in order to enable a rolling upgrade
between 2 different versions, yet compatible.
> add flag to disable completely version check in the TaskTracker and DataNode
> ----------------------------------------------------------------------------
>
> Key: HADOOP-8968
> URL: https://issues.apache.org/jira/browse/HADOOP-8968
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 1.2.0
>
> Attachments: HADOOP-8968.patch, HADOOP-8968.patch, HADOOP-8968.patch,
> HADOOP-8968.patch
>
>
> The current logic in the TaskTracker and the DataNode to allow a relax
> version check with the JobTracker and NameNode works only if the versions of
> Hadoop are exactly the same.
> We should add a switch to disable version checking completely, to enable
> rolling upgrades between compatible versions (typically patch versions).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
