hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6422) permit RPC protocols to be implemented by Avro
Date Mon, 14 Dec 2009 12:21:18 GMT

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

Steve Loughran commented on HADOOP-6422:

#  (minor) should we be really having .* imports.
#  -1 to logging the engine choice at info; makes client code extra noisy where it isn't of
interest to most people
# This changes the signature of some public methods; so needs to be marked up as a change
that is incompatible at the source level.
# RPC.waitForProxy with a timeout needs to be public, so callers can give up when the far
end isn't there. That's HADOOP-6435. 
# RPC.waitForProxy also needs to be interruptible, HADOOP-6221. Without that, you can't kill
a thread that is blocked

I will rebuild my patches for trunk to handle the latter two

> permit RPC protocols to be implemented by Avro
> ----------------------------------------------
>                 Key: HADOOP-6422
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6422
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: ipc
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 0.22.0
>         Attachments: HADOOP-6422.patch, HADOOP-6422.patch, HADOOP-6422.patch, HADOOP-6422.patch,
> To more easily permit Hadoop to evolve to use Avro RPC, I propose to change RPC to use
different implementations for clients and servers based on the configuration.  This is not
intended as an end-user configuration: only a single RPC implementation will be supported
in a given release, but rather a tool to permit us to more easily develop and test new RPC
implementations.  As such, the configuration parameters used would not be documented.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message