hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9924) [umbrella] Asynchronous HDFS Access
Date Wed, 01 Jun 2016 21:49:59 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311199#comment-15311199
] 

Jitendra Nath Pandey commented on HDFS-9924:
--------------------------------------------

  What is the expected timeframe for 2.8 release? Hopefully, we will settle on the API by
then. The code in trunk or branch-2 need not move out at all as 3.0 and 2.9 releases are still
far out. In the current shape, the code works and doesn't de-stabilize the branches and most
of the work is complete. Therefore, we don't need to hurry to move it out and add overhead
of merging it back.
Instead, we would try to expedite the convergence on the API. Based on discussion in HADOOP-12910,
it does seem like there is a lot of demand for Future with callback. We should plan to add
that, ideally in a way that works on both 3.x and 2.x. Reposting [~szetszwo]'s comment here:
bq. It seems that people really want Future with callback. I will think about how to do it...


> [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
>         Attachments: AsyncHdfs20160510.pdf
>
>
> 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)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message