You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2008/08/12 13:22:44 UTC
[jira] Created: (HADOOP-3936) JobClient should work with -1/+1
version of JobTracker
JobClient should work with -1/+1 version of JobTracker
------------------------------------------------------
Key: HADOOP-3936
URL: https://issues.apache.org/jira/browse/HADOOP-3936
Project: Hadoop Core
Issue Type: New Feature
Components: mapred
Environment: all
Reporter: Alejandro Abdelnur
Priority: Critical
Currently there is version check on the RPC calls that enforces the same Hadoop version on the client and the server.
To enable phased upgrades of systems using Hadoop and Hadoop itself the {{JobClient}} should be able to interact with a {{JobTracker}} of the previous and the next version of Hadoop (or with a range).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3936) JobClient should work with -1/+1
version of JobTracker
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621776#action_12621776 ]
Alejandro Abdelnur commented on HADOOP-3936:
--------------------------------------------
This could be done by either allowing a range version of clients on the {{JobTracker}}, or having an HTTP transport with potentially reduced functionality (like the HDFS over HTTP).
> JobClient should work with -1/+1 version of JobTracker
> ------------------------------------------------------
>
> Key: HADOOP-3936
> URL: https://issues.apache.org/jira/browse/HADOOP-3936
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Environment: all
> Reporter: Alejandro Abdelnur
> Priority: Critical
>
> Currently there is version check on the RPC calls that enforces the same Hadoop version on the client and the server.
> To enable phased upgrades of systems using Hadoop and Hadoop itself the {{JobClient}} should be able to interact with a {{JobTracker}} of the previous and the next version of Hadoop (or with a range).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3936) JobClient should work with -1/+1
version of JobTracker
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621876#action_12621876 ]
Alejandro Abdelnur commented on HADOOP-3936:
--------------------------------------------
And doing it as my second option? over HTTP to isolate rpc versions as HDFS over HTTP
> JobClient should work with -1/+1 version of JobTracker
> ------------------------------------------------------
>
> Key: HADOOP-3936
> URL: https://issues.apache.org/jira/browse/HADOOP-3936
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Environment: all
> Reporter: Alejandro Abdelnur
> Priority: Critical
>
> Currently there is version check on the RPC calls that enforces the same Hadoop version on the client and the server.
> To enable phased upgrades of systems using Hadoop and Hadoop itself the {{JobClient}} should be able to interact with a {{JobTracker}} of the previous and the next version of Hadoop (or with a range).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3936) JobClient should work with -1/+1
version of JobTracker
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621875#action_12621875 ]
Owen O'Malley commented on HADOOP-3936:
---------------------------------------
This requires more version tolerant rpc. The current version of rpc can't do it and so this is a big project.
> JobClient should work with -1/+1 version of JobTracker
> ------------------------------------------------------
>
> Key: HADOOP-3936
> URL: https://issues.apache.org/jira/browse/HADOOP-3936
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Environment: all
> Reporter: Alejandro Abdelnur
> Priority: Critical
>
> Currently there is version check on the RPC calls that enforces the same Hadoop version on the client and the server.
> To enable phased upgrades of systems using Hadoop and Hadoop itself the {{JobClient}} should be able to interact with a {{JobTracker}} of the previous and the next version of Hadoop (or with a range).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.