Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1B996188CA for ; Wed, 9 Mar 2016 01:49:42 +0000 (UTC) Received: (qmail 12305 invoked by uid 500); 9 Mar 2016 01:49:41 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 12138 invoked by uid 500); 9 Mar 2016 01:49:40 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 12110 invoked by uid 99); 9 Mar 2016 01:49:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Mar 2016 01:49:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id BDBE92C1F58 for ; Wed, 9 Mar 2016 01:49:40 +0000 (UTC) Date: Wed, 9 Mar 2016 01:49:40 +0000 (UTC) From: "Tsz Wo Nicholas Sze (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-9924) [umbrella] Asynchronous HDFS Access MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tsz Wo Nicholas Sze created HDFS-9924: ----------------------------------------- Summary: [umbrella] Asynchronous HDFS Access Key: HDFS-9924 URL: https://issues.apache.org/jira/browse/HDFS-9924 Project: Hadoop HDFS Issue Type: New Feature Components: fs Reporter: Tsz Wo Nicholas Sze Assignee: Xiaobing Zhou This is an umbrella JIRA for supporting Asynchronous HDFS Access. Currently, all the API methods are blocking calls -- the caller is blocked until the method returns. It is very slow if a client makes a large number of independent calls in a single thread since each call has to wait until the previous call is finished. It is inefficient if a client needs to create a large number of threads to invoke the calls. We propose adding a new API to support asynchronous calls, i.e. the caller is not blocked. The methods in the new API immediately return a Java Future object. The return value can be obtained by the usual Future.get() method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)