[
https://issues.apache.org/jira/browse/HADOOP-8968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-8968:
---------------------------------------
Attachment: HADOOP-8968.patch
Sure, Eli, thanks for the feedback.
Updated patch with following changes:
* renamed 'no.check' to 'skip.check'
* When 'skip.check' is TRUE we log both version and revision
* removed 'not' from comment
Eli, on your first bullet, about asserting an invalid build. I'd to leave it
like it is, without the build check; this allows experimental patches to be put
to try something. Also, depending on the SCM you are using (ie SVN or GIT)
defining an invalid build may be difficult.
> 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
>
>
> 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
