Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 58BFA19FEA for ; Sun, 20 Mar 2016 01:24:34 +0000 (UTC) Received: (qmail 90801 invoked by uid 500); 20 Mar 2016 01:24:34 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 90748 invoked by uid 500); 20 Mar 2016 01:24:34 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 90720 invoked by uid 99); 20 Mar 2016 01:24:34 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Mar 2016 01:24:34 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C04852C1F6F for ; Sun, 20 Mar 2016 01:24:33 +0000 (UTC) Date: Sun, 20 Mar 2016 01:24:33 +0000 (UTC) From: "Tsz Wo Nicholas Sze (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-12909) Change ipc.Client to support asynchronous calls MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-12909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203039#comment-15203039 ] Tsz Wo Nicholas Sze commented on HADOOP-12909: ---------------------------------------------- > ... Is there any cleaner way to do it? The reason of being implemented using ThreadLocal is that there are no easy ways to get the ipc.Client object from the caller, say DFSClient. The ipc.Client object is hidden very deep by Java [Proxy|http://docs.oracle.com/javase/7/docs/api/java/lang/reflect/Proxy.html] and the RpcEngine layer. If you could find some better ways to do it, please kindly let us know. > Change ipc.Client to support asynchronous calls > ----------------------------------------------- > > Key: HADOOP-12909 > URL: https://issues.apache.org/jira/browse/HADOOP-12909 > Project: Hadoop Common > Issue Type: New Feature > Components: ipc > Reporter: Tsz Wo Nicholas Sze > Assignee: Xiaobing Zhou > Attachments: HADOOP-12909-HDFS-9924.000.patch, HADOOP-12909-HDFS-9924.001.patch, HADOOP-12909-HDFS-9924.002.patch, HADOOP-12909-HDFS-9924.003.patch > > > In ipc.Client, the underlying mechanism is already supporting asynchronous calls -- the calls shares a connection, the call requests are sent using a thread pool and the responses can be out of order. Indeed, synchronous call is implemented by invoking wait() in the caller thread in order to wait for the server response. > In this JIRA, we change ipc.Client to support asynchronous mode. In asynchronous mode, it return once the request has been sent out but not wait for the response from the server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)