Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <634330581.1248129314813.JavaMail.jira@brutus>
Date: Mon, 20 Jul 2009 15:35:14 -0700 (PDT)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6132) RPC client opens an extra
 connection for VersionedProtocol
In-Reply-To: <840919907.1247085075163.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Raghu Angadi commented on HADOOP-6132:
--------------------------------------

sure. That is fine. If someone actually ends up using the interface, they will be similarly surprised. But for now I guess it is fine. If we want to fix it, we need to make the interface take class object as one of the arguments (since that is part of definition of what a connection is).

+1.


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