hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7227) Remove protocol version check at proxy creation in Hadoop RPC.
Date Mon, 02 May 2011 23:02:03 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027904#comment-13027904

Todd Lipcon commented on HADOOP-7227:

Making InterTrackerProtocol public got past that issue, but now hitting:

    [junit] java.lang.IllegalAccessError: tried to access class org.apache.hadoop.mapred.HeartbeatResponse
from class $Proxy7
    [junit]     at $Proxy7.heartbeat(Unknown Source)
    [junit]     at org.apache.hadoop.mapred.TaskTracker.transmitHeartBeat(TaskTracker.java:1692)
    [junit]     at org.apache.hadoop.mapred.TaskTracker.offerService(TaskTracker.java:1523)
    [junit]     at org.apache.hadoop.mapred.TaskTracker.run(TaskTracker.java:2428)
    [junit]     at org.apache.hadoop.mapred.MiniMRCluster$TaskTrackerRunner.run(MiniMRCluster.java:229)

I am going to temporarily revert this patch from common, since it was insufficiently tested
and is breaking the dependent projects.

> Remove protocol version check at proxy creation in Hadoop RPC.
> --------------------------------------------------------------
>                 Key: HADOOP-7227
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7227
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: 0.23.0
>         Attachments: HADOOP-7227.2.patch, HADOOP-7227.3.patch, HADOOP-7227.4.patch
> Currently when a proxy is created for a protocol, there is a round trip of messages to
check the protocol version. The protocol version is not checked in any subsequent rpc which
could be a problem if the server restarts with a new protocol version. This issue and also
the additional round-trip at proxy creation can be avoided if we add the protocol version
in every rpc, and server checks the protocol version for every call.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message