hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-677) RPC should send a fixed header and version at the start of connection
Date Tue, 21 Nov 2006 00:27:05 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-677?page=all ]

Doug Cutting updated HADOOP-677:
--------------------------------

        Status: Resolved  (was: Patch Available)
    Resolution: Fixed

I just committed this.  Thanks, Owen!

> RPC should send a fixed header and version at the start of connection
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-677
>                 URL: http://issues.apache.org/jira/browse/HADOOP-677
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.7.2
>            Reporter: Owen O'Malley
>         Assigned To: Owen O'Malley
>             Fix For: 0.9.0
>
>         Attachments: rpc-header.patch
>
>
> There have been problems with http clients connecting to the RPC servers, which causes
the RPC to try and allocate huge buffers and get OutOfMemoryExceptions. I want to have a fixed
prefix that is sent first that identifies it as an RPC client. To make the system compatible
as much as possible, I'd make the servers accept both forms for a Hadoop release and then
change the clients to send the prefix, and finally make the servers only accept the new form.

-- 
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

        

Mime
View raw message