[
https://issues.apache.org/jira/browse/HADOOP-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732743#action_12732743
]
Kan Zhang commented on HADOOP-6132:
-----------------------------------
> There is another instance of use of getDelaringClass() in the same file
Yes, it is used in a public static convenience method whereby users can make a
call by passing only the method. Unless we want to change the
interface contract and require the user to pass the protocol as well, we have
to use getDeclaringClass() to figure out the protocol. I'm not sure
what the original purpose of this interface was. But I feel it serves some
purpose (as long as users are aware of the twist of using
getDeclaringClass()) and since it is only used in tests, I don't feel making
the changes in this patch. What do you think?
> RPC client opens an extra connection for VersionedProtocol
> ----------------------------------------------------------
>
> Key: HADOOP-6132
> URL: https://issues.apache.org/jira/browse/HADOOP-6132
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: 1.patch, 2.patch
>
>
> RPC client caches connections per protocol. However, since all of our real
> protocols are subclasses of VersionedProtocol, a bug in the implementation
> makes the client opens an extra connection just for the VersionedProtocol,
> which is not needed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
