[
https://issues.apache.org/jira/browse/HADOOP-8968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484336#comment-13484336
]
Eli Collins commented on HADOOP-8968:
-------------------------------------
@Suresh,
The use case for this change is allowing a rolling upgrade when there is not an
exact version match, ie across minor releases in branch-1. Currently we
disallow that, from HADOOP-8209:
{quote}
In order to support this, let's add an option that is off by default, but, when
enabled, makes the DN and TT version check just check for an exact version
match (eg "1.0.2") but ignore the build revision (DN) and the source checksum
(TT). Two builds still need to match the major, minor, and point numbers, but
nothing else.
{quote}
@Tucu,
- Seems like we should still assert on invalid builds even if skip check flag
is used
- Should remove the "not" in "different versions are not permitted"
- Nit, feel free to ignore, I'd rename this hadoop.skip.worker.version.check
Otherwise looks good.
> 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
>
>
> 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
