hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-364) rpc versioning broke out-of-order server launches
Date Sat, 15 Jul 2006 00:13:14 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-364?page=all ]

Owen O'Malley updated HADOOP-364:

    Attachment: rpc-version-fix.patch

This patch:
  1. adds IOException to the getProtocolVersion method. All RPC methods need to declare this
exception so that the proxy object can throw IOException if there are communication problems.
  2. creates a RPC.VersionMismatch exception that can be caught and dealt with in a user friendly
  3. adds IOException to the signature for getProxy.
  4. adds RPC.waitForProxy that will loop waiting for the server to come up.
  5. make the TaskTracker and DataNode wait for their masters to come up.

> rpc versioning broke out-of-order server launches
> -------------------------------------------------
>                 Key: HADOOP-364
>                 URL: http://issues.apache.org/jira/browse/HADOOP-364
>             Project: Hadoop
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.5.0
>            Reporter: Owen O'Malley
>         Assigned To: Owen O'Malley
>             Fix For: 0.5.0
>         Attachments: rpc-version-fix.patch
> The change to check the RPCs broke the ability to bring up the datanodes before the namenode
and the tasktracker before the jobtracker.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message