hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9924) [umbrella] Asynchronous HDFS Access
Date Mon, 06 Jun 2016 16:55:21 GMT

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

Allen Wittenauer commented on HDFS-9924:

I'm not worried about code stability. branch-2 hasn't been rock-solid stable since 2.4; that
ship left the port years ago and every code dump into it in order to make press releases out
of features has just made it worse.  I'm much more worried about API correctness.  We're going
to be stuck with whatever is decided here for 5+ years, regardless of whatever the annotation
says. We've seen it with every other major API in Hadoop and I can't see why this would be
any different.  Waiting a while to actually let more folks play with it before pushing it
into a release (including the 3.x release that we're working to cut from trunk) just seems
like an obvious, common sense thing to do.

Also:  given that Andrew IS the RM for 3.x, him removing it from trunk is pretty much allowed.

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

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

View raw message